Skip to main content
Glama

Meeting notes

get_note

Notes the user typed in a meeting. Paged.

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_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNoFrom the previous page footer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and 'Paged' is the only real disclosure. It says nothing about permissions, what happens with an invalid or expired id, whether the note may be empty, ordering, or what the response contains. For a read tool with zero annotation coverage this is thin.

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

Conciseness3/5

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

Six words with no wasted phrasing, but the brevity is under-specification rather than economy. The content that exists is front-loaded, yet there is simply not enough of it to be useful.

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

Completeness2/5

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

With no annotations, no output schema, and half the parameters undocumented, the description should be doing the explanatory work and does not. An agent cannot tell from this definition what a valid call looks like, what comes back, or how paging terminates.

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

Parameters2/5

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

Schema coverage is 50%: the offset field is documented in the schema as coming 'from the previous page footer,' and 'Paged' echoes that. The required id parameter has no description in either the schema or the description, so the caller is left to infer that it identifies the meeting note and what form it takes.

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?

The fragment 'Notes the user typed in a meeting' identifies the resource and hints at the content type (user-typed notes, as opposed to a transcript or summary), but there is no verb saying it retrieves or fetches anything for a given note. An agent can guess the intent but must infer the action, and the distinction from siblings like get_transcript or get_summary is only implicit.

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 call this tool versus get_meeting, get_transcript, get_summary, or search_memory. 'Paged' is the only usage-adjacent hint, and it says nothing about which of the sibling retrieval tools to prefer.

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.