Skip to main content
Glama

Free Official Data Samples, Provenance, Aggregations & Insights

Recover a paid page

recover_dataset_page

Prove ownership of the paying wallet to recover the original page.

Input Schema

NameRequiredDescriptionDefault
operation_idNo
transaction_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that wallet ownership proof is required, but says nothing about side effects, reversibility, authentication mechanics, failure modes, or what recovery actually changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and contains no wasted wording, but it is too terse for a tool that requires choosing between two identifier parameters and proving wallet ownership.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and undocumented parameters, the definition should explain much more than the high-level recovery intent. It gives the core purpose and ownership prerequisite but leaves the invocation mechanics and outcomes largely unspecified.

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

Parameters1/5

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

There are two parameters with 0% schema description coverage and a oneOf requirement. The description does not mention operation_id or transaction_hash, explain when to use one versus the other, or clarify the required identifier format.

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 description states a specific verb and resource: recover the original page. It also adds a meaningful condition, proving ownership of the paying wallet, but does not explicitly distinguish this from sibling flows such as purchase_dataset_page_once or request_paid_access.

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?

The ownership condition implies when the tool is applicable, but there is no explicit when-to-use guidance, no exclusions, and no named alternative for related paid-access or purchase scenarios.

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