Skip to main content
Glama
Sign In
pepys-mcp

pepys-mcp

by ankurmans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List recent transcriptions

list_transcriptions
Read-onlyIdempotent

Retrieve recent transcription jobs with status, title, and duration to resume or export earlier results without re-transcribing.

Instructions

List this account's recent transcription jobs with their job_id, status, title, and duration, so you can resume, fetch, or export an earlier result instead of re-transcribing.

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": "list_transcriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool returns specific fields (job_id, status, title, duration) and mentions 'recent' jobs, implying ordering. It does not contradict annotations, but adds only moderate behavioral context beyond them.

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?

Two sentences, no wasted words. Every sentence adds value: first states the action and output, second states the purpose. Excellent front-loading.

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?

For a simple list tool with good annotations, the description provides sufficient context (resource, fields, purpose). It lacks mention of pagination or ordering details, but overall is adequate given the tool's simplicity.

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%, meaning the description does not explain the 'limit' or 'status' parameters. While the schema itself provides clear definitions (e.g., default, min, max, enum), the description should add contextual meaning but does not. This is a gap.

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 clearly states the verb 'list', the resource 'transcription jobs', and includes a specific purpose: 'so you can resume, fetch, or export an earlier result instead of re-transcribing.' It distinguishes itself from siblings like 'get_transcription' (single) and 'search_transcript' (search within content).

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 implies when to use ('instead of re-transcribing') but does not explicitly list when not to use or name alternative tools. However, the context is clear enough for an agent to decide.

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