Skip to main content
Glama

Visibility Genies

Recover a competitor refresh

recover_competitor_refresh

Reconcile interrupted work from saved evidence and ledger records only. No provider requests or new purchases. Uncertain outcomes must remain uncertain until proven; never automatically rebuy them.

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": {
      "projectId": "<projectId>",
      "id": "<id>"
    },
    "name": "recover_competitor_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, and destructiveHint=false, and the description usefully adds that no external requests or purchases occur and that uncertain outcomes must stay uncertain rather than being auto-rebought. It still doesn't say what local records get written or what the resulting state looks like.

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?

Three short sentences, front-loaded with the core action and followed by the hard constraints. No filler or restatement of the title.

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?

A mutating recovery tool with an output schema, so return values needn't be explained; the description covers the important safety constraints (no new requests, no auto-rebuy). The remaining gap is the unexplained 'id' parameter, which leaves the agent guessing what to pass.

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% for both required parameters (projectId and id), and the description adds no meaning to either — it never explains whether 'id' identifies the interrupted refresh, a ledger entry, or something else. The description does not compensate for the coverage gap.

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?

States a specific verb and scope: 'Reconcile interrupted work from saved evidence and ledger records only.' That distinguishes it from a fresh execution tool such as execute_competitor_refresh, though it never names the sibling explicitly.

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 phrase 'interrupted work' plus 'No provider requests or new purchases' clearly signals the recovery scenario and rules out using it when fresh provider data is needed. It stops short of naming an alternative tool to use for the non-recovery case.

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.

Resources