Skip to main content
Glama

TranscriptLab

Transcript library

transcriptlab_mentions
Read-onlyIdempotent

Composer at-mention search over the account’s transcript library, used to build the @TranscriptLab picker. App-facing only: the host calls it, it returns resource links rather than transcript text, and the model should not call it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transcriptlab_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoTypeahead text; may be empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds value beyond them by disclosing the return shape (resource links, not transcript text) and the caller restriction (host-invoked, not model-invoked). It does not discuss result limits or typeahead result caps, but for a picker endpoint that is a minor omission.

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

Conciseness5/5

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

Three short clauses with zero padding, and the critical constraint (model should not call it) is stated up front rather than buried. Every sentence carries distinct information: purpose, use case, caller restriction, and return type.

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?

For a one-parameter, no-output-schema endpoint, the description covers purpose, caller, and return shape completely. There is no output schema to explain, and the return-value nature is described in prose instead.

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% with a single documented parameter ("Typeahead text; may be empty"), so the schema already carries the parameter meaning. The description adds nothing further about query syntax or matching behavior, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("Composer at-mention search over the account's transcript library") plus the concrete use case ("build the @TranscriptLab picker"). It also distinguishes itself from the sibling transcript-retrieval tools by noting it "returns resource links rather than transcript text," so an agent can tell it apart without opening a schema.

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?

Gives an explicit exclusion: "App-facing only: the host calls it... and the model should not call it." This is the strongest possible when-not-to-use guidance and directly routes the agent away from this tool toward the transcript-reading siblings.

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.