Skip to main content
Glama

Coline

Get meeting notes

get_meeting_notes
Read-onlyIdempotent

Finds the note holding a meeting's notes, if there is one.

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": {
      "workspace": "<workspace>",
      "eventId": "<eventId>"
    },
    "name": "get_meeting_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
meetingNoteYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds the useful detail that the note may not exist, but says nothing about what is returned in that case. With an output schema present, return shape need not be described here.

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?

A single short sentence with the existence caveat front-loaded, so nothing is buried. The wording "the note holding a meeting's notes" is slightly circular, which costs a point but does not impede comprehension.

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?

This is a simple two-parameter read tool: annotations cover safety, the schema fully documents inputs, and an output schema covers returns. What remains is the existence caveat, which the description supplies. Only an explicit note about the no-note case would make it complete.

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%, and the schema already documents both eventId ("Event id from list_events") and workspace ("Workspace slug from workspaces.list"). The description adds no syntax, format, or cross-parameter meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource: finds the note associated with a meeting. It is unambiguous about what is retrieved, and the phrase "if there is one" flags that a note may not exist. It does not explicitly distinguish itself from siblings like get_note or get_meeting_summary, which keeps it from 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?

Usage is only implied: an agent can infer you call this when you have a meeting event and want its notes. There is no explicit when/when-not guidance and no mention of alternatives such as get_note for non-meeting notes. The absence is consistent with a simple lookup tool but leaves routing to inference.

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