Skip to main content
Glama

Physical Capability Cloud

get_ip_revenue

Read-only

Get the revenue PCC has recorded for an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue has been paid: any figure 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": "get_ip_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipIdYesIP asset ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds important behavioral context: no on-chain call occurs, nothing is registered/claimed/disputed, and any returned figure is a placeholder. This meaningfully helps an agent interpret the output, though it does not describe response shape or pagination.

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?

The main purpose is front-loaded in the first sentence, followed by important caveats about off-chain status and placeholder figures. The parenthetical branding note is slightly awkward but does not materially distract from the actionable guidance.

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 simple read-only tool with one fully documented parameter and no output schema, the description provides enough context about what is being returned and the placeholder caveat. It could be more complete by stating whether the response includes metadata or only the revenue figure, but the core call context is present.

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%, and the sole parameter ipId is already documented as the IP asset ID. The description adds no additional syntax, format, or lookup semantics beyond the schema, so it meets the baseline for high schema coverage.

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: getting PCC-recorded revenue for an IP asset. It does not explicitly distinguish this from the sibling claim_ip_revenue or explain how the recorded figure differs from a claimable amount, so it stops short of full sibling differentiation.

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 description implies this is an off-chain reporting/read operation by saying these tools make no on-chain call and no revenue has been paid. However, it does not explicitly say when to use this instead of claim_ip_revenue or other revenue-related siblings.

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.