Retrieve the Webex teams you can access, with an optional maximum result count, to identify teams for collaboration or management tasks.
List accessible teams.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "webex_list_teams"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| max | No |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden and largely fails it. 'Accessible' hints at a permission scope, but there is no mention of pagination behavior, whether results are truncated, or what a page of teams looks like.
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?
It is a single short sentence with no wasted words, but it is under-specified rather than genuinely concise. There is nothing to be front-loaded because so little is said.
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?
For a list tool with no annotations and no output schema, the description should at minimum address scope and pagination. Neither is present, leaving the agent unable to predict result volume or how to page through teams.
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?
The single parameter 'max' has 0% schema description coverage and is not mentioned in the description at all, so its role as a page-size limit (default 100, maximum 1000) is left undocumented. The description adds no parameter meaning beyond the bare schema.
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?
The description gives a verb and resource ('List ... teams'), so the basic operation is identifiable. But 'accessible' is undefined (accessible to the authenticated user? to an org?) and nothing distinguishes this listing of teams from sibling listing tools such as webex_list_spaces or webex_list_team_memberships.
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?
There is no guidance on when to use this instead of alternatives like webex_get_team or webex_list_team_memberships. The agent must infer usage entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.