Skip to main content
Glama

Physical Capability Cloud

get_capability_ip

Read-only

Get the IP record PCC holds for a capability by its capability ID. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any id or transaction hash in it 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": {
      "capabilityId": "<capabilityId>"
    },
    "name": "get_capability_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
capabilityIdYesCapability ID to look up IP registration for

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds real value by disclosing that no on-chain calls are made and that nothing is registered, claimed or disputed on chain. The warning that any id or transaction hash returned is a placeholder is exactly the kind of behavioral caveat annotations cannot express. It does not cover empty-result or data-freshness behavior, which keeps it from a 5.

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 core purpose is front-loaded in one clean sentence, and the caveats follow in short statements. The fragment 'Story Protocol (now The DATA Foundation).' is a standalone sentence with no verb and reads like boilerplate, slightly weakening the structure, but nothing is redundant.

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 one-parameter read tool with no output schema, the description covers what is looked up, what is returned conceptually (the IP record PCC holds), and a critical caveat about the data's off-chain, placeholder nature. What is missing is only marginal: behavior on a missing capability ID and the record's fields.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines capabilityId fully. The description only restates 'by its capability ID' without adding format, sourcing, or validity constraints, so the baseline 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?

States a specific verb ('Get') and resource ('the IP record PCC holds for a capability') plus the lookup key (capabilityId), which is enough to separate it from the write-side sibling register_capability_ip and from get_ip_lineage/get_ip_revenue. It stops short of naming any alternative explicitly, but the purpose itself is unambiguous.

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 only implied: 'look up IP registration for a capability ID.' There is no statement of when to prefer this over get_ip_lineage or get_ip_revenue, no preconditions, and no exclusion of the registration tool. An agent must infer the routing from the resource noun.

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.