Skip to main content
Glama

end_collaboration

Destructive

Close an active collaboration and optionally request a summary of key agreements, disagreements, and action items; prototype sessions also return outcomes and the human shortlist.

Instructions

End a collaboration and optionally get a summary of the discussion. Prototype sessions also return the prototype outcomes and the shortlist for the human (resolved prototypes appear as stubs in the transcript).

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": {
      "collaboration_id": "<collaboration_id>"
    },
    "name": "end_collaboration"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_summaryNoIf true, ask an agent to summarize key agreements, disagreements, and action items.
collaboration_idYesThe collaboration ID to end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful prototype-session return behavior and the stub representation, but it does not explain what ending a collaboration destroys or whether the action is reversible beyond what the annotations imply.

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?

Two sentences, front-loaded with the primary action and no obvious padding. The parenthetical about resolved prototypes is dense but conveys relevant return behavior.

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

Completeness3/5

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

For a destructive end tool with no output schema, the description covers the optional summary and prototype returns, which is helpful. However, it omits what happens to the collaboration state or transcript and does not resolve when this tool should be used instead of sibling ending tools.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents both parameters; baseline is 3. The description adds that request_summary yields key agreements, disagreements, and action items, and that prototype sessions return outcomes automatically, but it does not add conditions or format details for collaboration_id.

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?

States a specific verb and resource: 'End a collaboration' plus the optional summary behavior. It does not differentiate from sibling ending tools such as end_meeting, end_local_meeting, or end_ultraplan, so an agent must infer the target resource from the name alone.

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

Usage Guidelines3/5

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

Usage is implied by the name and by 'optionally get a summary of the discussion,' but there is no explicit when-to-use or when-not guidance. It also does not tell the agent when to choose this over continue_collaboration, pause_collaboration, or the other end_* siblings.

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