Skip to content

Commit 78f8516

Browse files
committed
Add note about the visibility of Groups to LLMs
1 parent aadf095 commit 78f8516

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

seps/2084-primitive-groups.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,11 @@ Groups are named collections of MCP primitives: tools, prompts, resources, tasks
3737
- So `email_thank_contributor` would appear in both `email` and `communications`.
3838
- Some clients might wish to only show direct children of a group.
3939

40+
#### Visibility of Groups to LLMs
41+
- Groups are simply an organizational tool available to the server developer.
42+
- It is up to clients to decide how to interpret and make use of them, e.g., for deciding what primitives to expose to LLMs or simply ignoring them.
43+
- Server developers cannot expect that clients will pass any group information to LLMs, although they may.
44+
4045
### Why use Groups?
4146

4247
Organizing a server's primitives by functionality or use case enables richer client workflows, wherein certain operations or settings can be applied to multiple primitives concurrently. Some use cases [identified by the community](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/1772) include:

0 commit comments

Comments
 (0)