Skip to main content
Glama

Physical Capability Cloud

distribute_royalties

Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue is paid from these splits.

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>",
      "splits": "<splits>"
    },
    "name": "distribute_royalties"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipIdYesIP asset ID
splitsYesRevenue splits — must sum to 100

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?

The annotations say this is a non-read-only but non-destructive operation, and the description adds important behavioral context: it makes no on-chain call, registers/claims/disputes nothing, and pays no revenue. It does not cover persistence, permissions, or reversibility, so it falls short of fully rich behavioral disclosure.

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 constraint and off-chain caveat are front-loaded and easy to scan. The mention of 'Story Protocol (now The DATA Foundation)' and the repeated no-revenue point are slightly extra, but overall the description is efficiently structured.

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 configuration tool with complete schema descriptions and no output schema, the definition covers the key semantics: stakeholder splits, the 100% sum rule, and the fact that nothing is claimed or paid on chain. It could be more complete only by adding operational prerequisites or what happens after the call persists.

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?

The input schema already has 100% description coverage, including meanings for ipId, splits, role, address, label, and percentage. The description reinforces the stakeholder roles and the sum-to-100 constraint but does not add substantial meaning beyond the schema.

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: setting revenue splits for an IP asset among named stakeholder roles. It is clear what the tool does, but it does not explicitly distinguish itself from similarly named revenue or claim tools by naming an alternative.

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 implied by the statement that the tool sets splits and does not pay revenue or make on-chain claims. However, it gives no explicit when-to-use guidance or named alternative for related operations such as claiming revenue.

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.