Skip to main content
Glama

Search meetings

search
Read-onlyIdempotent

Find what was discussed, decided, assigned, or promised in work call transcripts and summaries, including deadlines and task status. Filter by date, then read matching meetings.

Instructions

Search the user's work calls: transcripts (who said what) and summaries (decisions, tasks, open questions).

Use it first when a question is about what was discussed, decided or agreed, who assigned or promised what, deadlines, the status of tasks and projects, or colleagues. People ask things like "What did we decide about pricing?", "What did Maya promise to send me?", "When did we last talk about the API migration?", "Did anyone push back on the Thursday release?" Matches words with different endings. Ranked by how many query words matched, then newest first. Then read what you found with get_meeting and get_transcript. Read-only.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches to return
queryYesKeywords in the language of the meetings themselves, as they were said on the call: topic, name, project
sinceNoDate YYYY-MM-DD, inclusive; empty — no bound
untilNoDate YYYY-MM-DD, inclusive; empty — no bound

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavioral detail not present in structured fields: stemming ("Matches words with different endings") and an explicit ranking rule ("how many query words matched, then newest first"). That ranking disclosure materially affects how an agent interprets and reports result order.

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 definition is front-loaded with purpose, then usage, then matching/ranking, then next steps — a sensible order with no filler sentences. It runs long partly from four illustrative example questions, which aid intent mapping but could be trimmed without losing meaning.

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

Completeness5/5

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

An output schema exists, so return-shape explanation is unnecessary, and annotations cover safety. The description supplies what structured fields cannot: the semantic scope of matches, ranking behavior, and the follow-up read path. Nothing an agent needs to call and interpret this tool correctly is missing.

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%, so query, limit, since and until are already fully documented with formats and defaults. The description's phrasing about query language overlaps the schema text rather than extending it, and it says nothing about limit or date-bound interactions. Baseline 3 is appropriate when the schema carries the parameter burden.

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

Purpose5/5

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

The description opens with a specific verb and resource — "Search the user's work calls: transcripts (who said what) and summaries" — and scopes exactly what is searched. This clearly separates it from get_meeting/get_transcript (which fetch one item) and list_meetings (which enumerates), so an agent can route without inspecting other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use conditions (questions about what was discussed, decided, assigned, deadlines, status, colleagues) and a concrete follow-up path: "Then read what you found with get_meeting and get_transcript." The "use it first" instruction plus named downstream tools resolves the ordering ambiguity between siblings.

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

Deploy Server

Other Tools