Skip to main content
Glama

Reachout recovery meetings

Get one meeting

get_meeting
Read-onlyIdempotent

One meeting by its reachout_id.

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": {
      "id": "<id>"
    },
    "name": "get_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe meeting's reachout_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered without the description. The description adds nothing beyond that: no note on behavior for a missing or stale reachout_id, no indication of whether a null/empty result is returned, and no sense of what a returned meeting contains.

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 sentence fragment is short, front-loaded, and free of filler, so nothing is wasted. Its brevity reflects under-specification rather than good editing, but on the conciseness axis alone it is efficient.

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?

This is a simple one-parameter read with rich annotations and a fully documented schema, and there is no output schema, so the description should at least characterize the returned meeting. It does not, leaving the agent to guess at the response shape, but the overall complexity is low enough that the gap is modest.

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 description coverage is 100% and the single parameter is documented as "The meeting's reachout_id." The description merely echoes that wording, adding no format, provenance, or lookup hints (for example where a reachout_id can be obtained). Baseline 3 applies when the schema already carries the parameter meaning.

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

Purpose3/5

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

"One meeting by its reachout_id" does signal a single-record lookup keyed on reachout_id, which separates it from the list_/find_ siblings in spirit. But the phrasing is a noun fragment with no verb and largely restates the name and title "Get one meeting", so the agent must infer that this is a fetch-by-identifier rather than something that computes or derives a meeting.

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 statement of when to use this tool versus find_meetings_near, list_meetings_in_area, or find_online_meetings, and no mention of what to do if the reachout_id is unknown. The only implicit guidance is that an id is required, which the schema already enforces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources