ZeroHrs MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Get Zero Transcript

get_transcript

Read-onlyIdempotent

Retrieve a summary for any ZeroHrs transcript by ID, with optional linked tasks and query-matched speaker blocks plus adjacent context, without loading every turn.

Instructions

Get a transcript summary by id. Optionally include linked tasks and query-matched speaker blocks with adjacent context. This never loads every transcript turn.

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": {
      "transcript_id": "<transcript_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

Name	Required	Description
`turn_limit`	No
`turn_query`	No
`include_tasks`	No
`transcript_id`	Yes	Known Zero transcript id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context that "This never loads every transcript turn" and describes optional inclusion of tasks and query-matched blocks, but it does not disclose what the summary contains or mention any response limits beyond the schema.

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?

The description is two sentences with the primary action front-loaded. It is concise, scannable, and every sentence adds value without redundancy.

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?

For a 4-parameter tool with no output schema, the description covers the main purpose and two optional behaviors, but fails to explain turn_limit or define what the transcript summary includes. It is adequate for basic invocation but not fully complete.

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 only 25%, so the description must compensate. It indirectly explains include_tasks ("linked tasks") and turn_query ("query-matched speaker blocks with adjacent context"), but turn_limit is not mentioned or clarified, leaving a meaningful gap for agent understanding.

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?

The description clearly states a specific action and resource: "Get a transcript summary by id." The word "summary" distinguishes this from list/search transcripts, though it does not explicitly name a sibling alternative for contrast.

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?

The description makes clear this tool is for retrieving a single transcript summary when you have a transcript id, with optional extensions for tasks and query-matched speaker blocks. It does not explicitly state when to prefer list_transcripts or search_transcripts, but the "by id" context provides adequate guidance.

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