Skip to main content
Glama

TranscriptLab

Check TranscriptLab usage

transcriptlab_get_usage
Read-onlyIdempotent

Read the account plan, remaining credits, and current-period usage. Use when the user asks about cost, balance, or limits, or before a credit-spending request.

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_get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds value beyond them by enumerating what is returned (plan, credits, current-period usage) — the only disclosure of return contents, since no output schema exists — and by framing it as a pre-spend check. It omits freshness/units of the credit figures and any auth or rate-limit notes.

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 tight sentences: what it reads first, when to call it second. No filler, no restatement of the title, and the return contents are front-loaded where an agent will read them.

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 zero-argument read tool with rich annotations but no output schema, the description carries the return-value burden and does so by listing the three data groups. Only minor gaps remain — whether usage is a live or snapshot figure and what units credits use — which would help an agent interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the object schema with additionalProperties=false confirms no arguments are needed. The baseline for a no-parameter tool applies, and nothing in the text misleads about inputs.

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 names a specific verb and a concrete set of resources: 'Read the account plan, remaining credits, and current-period usage.' That is immediately distinguishable from every sibling, which all deal with transcript retrieval, transcription, jobs, or links, so an agent can route on the description alone.

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?

It gives explicit triggers — 'when the user asks about cost, balance, or limits' — plus a proactive trigger, 'before a credit-spending request,' which is genuinely actionable pre-flight guidance. It stops short of stating when not to call it or naming any alternative, but no sibling overlaps in this domain, so the guidance is close to complete.

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.