Skip to main content
Glama

media_retry_recovery

Make unfinished [cvrt] Media records due again (needs [cvrt] Media 0.1.1+): resets the back-off counters only, never touches a file; the runner's next pass works them.

Instructions

Make unfinished [cvrt] Media records due again (needs [cvrt] Media 0.1.1+): resets the back-off counters only, never touches a file; the runner's next pass works them. Needs exactly one scope: ids (attachment ids, at most 500) or all: true (every stuck record). Returns { retried, counts }.

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": {
      "site": "<site>"
    },
    "name": "media_retry_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoScope: true retries every stuck record
idsNoScope: attachment ids to retry, at most 500
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations the description carries the full burden and does well: it discloses the version dependency (0.1.1+), that only counters are reset, that no file is touched, and that work happens on the runner's next pass. It omits permission requirements and error behavior when neither or both scopes are supplied.

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?

Densely packed into a few clauses with the core effect front-loaded, and every clause carries information (constraint, safety, return shape). Slightly overloaded with bracketed vocabulary and parentheticals, but nothing is filler.

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 three-parameter mutation tool with no annotations and no output schema, the description covers purpose, safety, scope constraint, version prerequisite, and return shape. There is nothing material an agent needs to call it correctly that is missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a mutual-exclusivity rule the schema cannot express: 'needs exactly one scope: ids (at most 500) or all: true'. This directly prevents an invalid call.

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 effect ('make unfinished [cvrt] Media records due again') plus the precise mechanism ('resets the back-off counters only'), which clearly separates it from status-inspection siblings such as media_get_recovery. An agent knows exactly what this changes before opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the target state ('unfinished' / 'stuck' records in back-off) but never stated as a when-to-use rule, and no alternative tool is named for inspecting or deleting those records. The 'exactly one scope' constraint is a parameter rule, not guidance on choosing this tool.

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