Skip to main content
Glama
Sign In
Reedapt MCP server

Reedapt MCP server

Official
by Reedapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get usage

get_usage
Read-only

Check account plan, key status, and remaining minutes before a long dub to verify sufficient capacity. Retrieve monthly usage reports by key and language.

Instructions

The account's plan, whether the key is live or test, and the minutes left. Check this before a long dub: a live dub uses one minute of the plan per minute of video, per language. Test keys are free and dub only the first seconds with a watermark.

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

Input Schema

NameRequiredDescriptionDefault
monthNoA month as YYYY-MM for that month's usage report, by key and language. Leave out for the current balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description nonetheless adds real context beyond them: the minute-per-minute-per-language billing cost and the free-but-watermarked test-mode behavior. It omits pagination, error behavior on invalid months, and whether historical month reports differ from the current balance beyond the schema hint.

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?

Three short sentences, front-loaded with what is returned before the advisory text, with no filler. The opening is a noun-phrase fragment, which is slightly less scannable than a verb-led statement but not wasteful.

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?

There is no output schema, and the description names the returned fields (plan, live/test key, minutes left) but not their types or shape, nor what a month-scoped report returns versus the current balance. The billing context is solid, but return-value completeness is only partially covered for a tool with no output schema.

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% and the schema documents the single optional month parameter with a YYYY-MM pattern and the 'current balance' default. The description adds no format or semantics beyond that, so the baseline of 3 applies.

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 first sentence names the specific resource and its three return values: plan, key mode (live/test), and remaining minutes. The month-scoped usage report implied by the parameter is not mentioned, so the tool's scope is slightly narrower in the description than in the schema. It does not single out a sibling to distinguish against, though no sibling competes for the same data.

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?

Explicit trigger given: 'Check this before a long dub,' with a stated rationale (a live dub burns one plan minute per video minute, per language). It also tells the agent how test keys behave (free, watermarked, truncated). No explicit 'when not to use' is stated, but the positive guidance is concrete enough to drive selection.

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