Skip to main content
Glama

end_meeting

Destructive

Close a meeting by ID and optionally request a summary; prototype meetings also return outcomes and a human shortlist.

Instructions

End a 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_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYesThe 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
Behavior4/5

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

Beyond the destructive and non-idempotent annotations, the description discloses the optional summary and the additional outcomes and shortlist returned for prototype meetings. It still leaves the finality of closure and the default result for non-prototype meetings unstated.

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

Conciseness5/5

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

Two short sentences front-load the primary action and then provide one useful special case. There is no redundant or distracting wording.

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?

The two well-documented parameters and safety annotations make this sufficient for basic invocation, and the prototype return note partly compensates for the missing output schema. However, unclear sibling scope, closure semantics, and ordinary return behavior leave noticeable gaps for confident selection and use.

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?

Both meeting_id and request_summary already have clear schema descriptions, including that the summary is requested before ending. The description's phrase 'optionally get a summary' adds little beyond that complete schema coverage.

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 opening sentence gives a specific action and resource—ending a meeting—with an optional summary, while the second identifies prototype-specific results. It does not clarify how this differs from siblings such as end_local_meeting, so it stops short of full differentiation.

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?

There is no explicit guidance about when to choose this tool, which meeting types it accepts, or when another ending tool is more appropriate. The prototype sentence describes returned data rather than providing a selection condition or exclusion.

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