Skip to main content
Glama

Find or open a meeting

get_meeting

A recorded meeting: when, who spoke, and which parts exist (get_note, get_summary, get_transcript). Without id, finds meetings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
queryNoWords said or a YYYY-MM-DD date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the payload shape (timing, speakers, available parts), which is genuinely useful. It is silent on whether the tool is read-only, on permissions, on how many results a no-`id` search returns, and on what happens when both `id` and `query` are supplied.

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 compact clauses, no filler, and the resource definition is front-loaded ahead of the find-vs-open rule. The compressed fragment style makes the opening slightly harder to parse than a plain verb-first sentence would be.

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?

With only two optional parameters, no annotations, and no output schema, the description covers the essentials: what the record contains and the two operating modes. It stops short of describing search behavior or result limits, which an agent would need before relying on the no-`id` mode.

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 50%: `query` is documented in the schema ('Words said or a YYYY-MM-DD date') but `id` is not, and the description partially compensates by implying `id` selects a single meeting while its absence triggers search. It adds no detail on matching semantics for `query` or on precedence when both parameters are given.

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 defines the resource concretely ('when, who spoke, and which parts exist') and enumerates the constituent parts via sibling tools (get_note, get_summary, get_transcript), which lets an agent distinguish this tool from those. The opening is a noun-phrase fragment rather than a verb+resource statement, and the dual find/open behavior only appears in the second sentence, so it falls short of a 5.

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?

It gives one useful conditional: omit `id` to search for meetings, supply `id` to open one. The sibling parenthetical also implicitly routes the agent to get_note/get_summary/get_transcript for detail. However, there is no guidance on when to prefer this over search_memory, and no stated exclusions or prerequisites.

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.