Skip to main content
Glama
Sign In
mcp-agent-collaboration

mcp-agent-collaboration

by vkolotov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

leave_topic

Exit a joined topic by providing its join token to stop message delivery and end participation.

Instructions

Leave the joined topic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "join_token": "<join_token>"
    },
    "name": "leave_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
join_tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of disclosing behavior. It states the action 'leave' but does not disclose side effects, prerequisites, required permissions, or whether the action is reversible. For a mutation tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, making it extremely concise and front-loaded. Every word is essential, but its brevity sacrifices necessary context, so it is not as effective as it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's simplicity and the presence of an output schema, the description is incomplete. It lacks any context about when to leave a topic, what happens after leaving, or any dependencies on prior actions like joining. The agent is left to infer the tool's role from the parameter and siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention the join_token parameter at all. Schema coverage in the description is 0%, so the agent receives no help understanding what the token is, how to obtain it, or its role in leaving the topic. The parameter name alone is not sufficient to convey its purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Leave the joined topic' uses a clear verb+resource structure, indicating the action of leaving a topic. It is distinct from sibling tools like join_topic, though it does not explicitly clarify whether 'joined topic' refers to the current session or the topic identified by join_token, leaving slight ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that it should be used after joining a topic, nor does it note any exclusions or conditions. There are no references to sibling tools or when to prefer this over others.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools