Skip to main content
Glama

Physical Capability Cloud

register_capability_ip

Record a capability as an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any ipId, NFT token id or transaction hash in the reply is a placeholder, and no royalty is paid.

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": {
      "capability": "<capability>",
      "designerAddress": "<designerAddress>",
      "designerName": "<designerName>"
    },
    "name": "register_capability_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipfsCidNoIPFS CID of the capability spec document (optional)
capabilityYesCapability object
designerNameYesDisplay name of the designer
designerAddressYesEVM address of the capability designer
commercialRevShareNoRevenue share percentage for commercial use (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The description adds meaningful context the annotations cannot: despite readOnlyHint=false the operation performs no on-chain registration, and any ipId, NFT token id or transaction hash returned is a placeholder. That is exactly the kind of side-effect disclosure an agent needs. It omits persistence details (whether a local record is still written) and any auth requirements.

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 action is front-loaded in one clause and the caveats follow compactly. The parenthetical 'Story Protocol (now The DATA Foundation)' is contextual branding that does not help an agent invoke the tool and slightly dilutes an otherwise tight description.

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

Completeness3/5

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

For a tool with a nested object parameter and no output schema, the description correctly pre-empts confusion about placeholder return values without needing to enumerate fields. However, it does not clarify what is persisted after the call or whether the placeholder result can be used by get_capability_ip, which leaves real gaps for a five-parameter write-shaped tool.

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 every parameter is already documented, including the nested capability object and the 0-100 commercialRevShare. The description adds no parameter meaning beyond the schema and does not explain the role of designerAddress or the optional ipfsCid. 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?

The first sentence names a specific verb and resource: 'Record a capability as an IP asset.' An agent can tell this is an IP-asset recording tool, distinct from read tools like get_capability_ip. It does not explicitly differentiate itself from the sibling create_capability, so it stops short of a 5.

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 statement of when to use this versus create_capability, get_capability_ip, claim_ip_revenue, or raise_ip_dispute. The closest thing to guidance is the negative 'these tools make no on-chain call,' which explains behavior rather than selecting between tools. The agent must infer the choice from sibling names 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.