Skip to main content
Glama

Metis ยท Meeting Memory โ€” Enrich Meeting With Crossrefs

enrich_meeting_with_crossrefs

Extract key topics from a saved meeting transcript and match them against open tasks, library papers, and active projects to return a structured cross-reference brief.

Instructions

Find cross-references for a saved meeting: open tasks, related papers, active projects.

Call this after saving a meeting transcript (via Meetings tab or
transcribe_recording()). It extracts key topics from the transcript,
matches them against tasks, library papers, and active projects, and
returns a structured cross-reference brief.

The result is also written to the meeting's notes field in the database
so it appears in the Meetings tab.

Args:
    meeting_id: The meeting_id from the meetings table.

Returns:
    Formatted cross-reference brief listing matched tasks, papers, and projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, description carries full burden. It discloses that the result is written to the meeting's notes field in the database, which is a side effect. However, it doesn't discuss permissions, rate limits, or other behavioral aspects.

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?

Well-structured with a short summary, followed by usage context, behavior, and args/returns sections. No unnecessary sentences, but could be slightly more concise.

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?

Given a single parameter and existing output schema, the description covers the tool's purpose, usage context, side effects, and return value. It is complete enough for a tool with this complexity.

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?

Only one parameter (meeting_id) with 0% schema description coverage. Description adds 'The meeting_id from the meetings table', providing context beyond the schema's 'Meeting Id' title, but could offer more detail like format or example.

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?

Description clearly states the verb 'find cross-references' and the resource 'saved meeting', specifying the types of cross-references (open tasks, related papers, active projects). It distinguishes from siblings by focusing on enriching a meeting after saving its transcript.

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

Usage Guidelines4/5

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

Explicitly says 'Call this after saving a meeting transcript' and mentions the normal flow via Meetings tab or transcribe_recording(). Does not provide when-not-to-use or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server