Skip to main content
Glama

end_local_meeting

Destructive

Close a local meeting by meeting ID, optionally request an agent summary, and retrieve prototype outcomes and a human shortlist for prototype meetings.

Instructions

End a LOCAL meeting and optionally get a summary. Prototype meetings also return the prototype outcomes and the shortlist for the human.

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": {
      "meeting_id": "<meeting_id>"
    },
    "name": "end_local_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYesThe local meeting ID to close.
request_summaryNoIf true, ask the agent for a summary before ending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds that prototype meetings return prototype outcomes and a shortlist for the human, which is genuinely new behavioral context, but it never says what state is destroyed or whether ending is reversible, and 'optionally get a summary' is vaguer than the schema's 'ask the agent for a summary before ending'.

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 short sentences, front-loaded with the core action and no filler. The second sentence is dense but earns its place by disclosing prototype-specific returns; the only weakness is the ambiguous 'optionally get a summary' phrasing.

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

Completeness4/5

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

There is no output schema, and the description partially compensates by naming what comes back (summary, prototype outcomes, shortlist). For a destructive two-parameter tool it is close to sufficient, though it omits any note on error cases like an already-ended or unknown meeting_id.

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 both parameters are already documented. The description only loosely restates request_summary as 'optionally get a summary', which is slightly at odds with the schema's 'ask the agent for a summary before ending', and adds no new detail about meeting_id. Baseline 3 is correct when the schema does the heavy lifting.

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?

Specific verb+resource: "End a LOCAL meeting", with the 'LOCAL' qualifier distinguishing it from the sibling end_meeting. It also states the optional summary and the special return content for prototype meetings. It stops short of naming end_meeting as the non-local counterpart, so the differentiation is implied rather than explicit.

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: call this when you want to close a local meeting and possibly obtain a summary, and expect extra outputs for prototype meetings. There is no explicit when-to-use vs end_meeting/end_collaboration guidance and no stated preconditions such as the meeting needing to be active or who may end it.

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