groove_list_teamsList teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Relay pagination cursor — pass the previous page's `endCursor` to get the next page. | |
| first | No | How many records to return (Relay pagination `first`). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds pagination behavior beyond annotations (readOnlyHint=true). No contradictions. Could include rate limits or further details, but annotations cover safety.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences: purpose, pagination, underlying API. No wasted words, front-loaded with core info.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, and description omits return format (e.g., team IDs, names). Mentions GraphQL but insufficient for an agent to anticipate response structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed descriptions for 'after' and 'first'. Description merely restates 'Paginate with first/after', adding minimal new meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb 'list' and resource 'teams'. Explanation that teams are groups of agents for conversation assignment distinguishes from sibling tools like groove_list_agents and groove_list_conversations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides pagination guidance ('first/after') but lacks explicit when-to-use versus alternatives or when-not-to-use context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.