Skip to main content
Glama

Physical Capability Cloud

claim_ip_revenue

Claim an IP asset's recorded revenue. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Nothing is paid out: any amount or transaction hash in the reply is a placeholder.

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": {
      "ipId": "<ipId>"
    },
    "name": "claim_ip_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipIdYesIP asset ID
tokenIdsNoSpecific royalty token IDs to claim (optional — claims all if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the genuinely important disclosure that no on-chain call occurs, nothing is registered/claimed/disputed, and returned amounts or tx hashes are placeholders. That materially changes how an agent should interpret and report the result. It stops short of stating permission requirements, idempotency, or whether any off-chain state is written.

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 with the action front-loaded and the simulation caveat immediately after; no sentence is filler. The one weak element is the parenthetical 'Story Protocol (now The DATA Foundation)', which is branding rather than operational information, but it costs almost nothing.

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 two-parameter tool with full schema coverage and no output schema, the description covers the critical thing an agent would otherwise get wrong: that the response is a simulation with placeholder values. It could still say whether a recorded-revenue entry must exist or what errors look like, but nothing essential is missing.

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 description coverage is 100%, so both ipId and tokenIds are already documented, including the 'claims all if omitted' default. The description adds no further meaning about these parameters, 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 opening sentence gives a specific verb and resource — 'Claim an IP asset's recorded revenue' — which cleanly separates it from the read-side sibling get_ip_revenue. The remainder of the description is caveats rather than further scope definition, so the purpose is clear but not richly elaborated (e.g., it never says what a claim does off-chain if it does nothing on-chain).

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as get_ip_revenue (to inspect revenue) or distribute_royalties. The only conditional signal is the implicit 'recorded revenue' phrasing; an agent must infer the selection logic from the tool name alone.

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.