Skip to main content
Glama

meetings

Search recorded Memoir calls to retrieve transcripts, summaries, notes, and prep, returning matching snippets with dates and file references.

Instructions

Search recorded meetings (Memoir calls) — transcripts, summaries, notes and prep.

    Each hit names its call: ``meeting`` (folder ``YYYY-MM-DD_<name>``), ``date``, ``file``
    (``transcript.txt`` | ``summary.md`` | ``notes.md`` | ``prep.md``), plus ``symbol``
    (transcript speakers + time range, or the summary section) and the snippet.
    

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": {
      "text": "<text>"
    },
    "name": "meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the hit structure — meeting folder, date, file, symbol, and snippet — which tells the agent what comes back, but it says nothing about permissions, result limits, ranking, or whether the operation is purely read-only (only implied by 'Search').

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 blocks: a one-line purpose statement followed by the hit shape. The RST double-backtick markers add minor visual noise but no wasted sentences; the purpose is front-loaded.

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?

An output schema exists, so explaining return values is optional, and the description's hit-shape enumeration is a reasonable bonus. However, for a two-parameter search tool with zero schema description coverage and no annotations, the missing explanation of 'k' and 'text' leaves a real completeness gap.

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 description coverage is 0% for the two parameters, so the description must compensate and it does not. The required 'text' query string is only implied by the word 'Search', and the 'k' integer (default 5) is never mentioned at all, so the agent cannot know it controls the number of hits.

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: 'Search recorded meetings (Memoir calls) — transcripts, summaries, notes and prep.' The parenthetical and the enumerated content types make the scope concrete. It does not differentiate itself from siblings like query, recall, or get, leaving the agent to infer that this one is recording/transcript-specific.

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 when-to-use or when-not-to-use guidance and no alternative tool is named, even though siblings such as query, recall, and lessons plausibly overlap. The agent must infer from the phrase 'recorded meetings' alone that this tool is the right choice for transcript/prep lookups.

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