Skip to main content
Glama

Physical Capability Cloud

get_ip_lineage

Read-only

Get the IP lineage PCC has recorded for an asset: parent capabilities and derivative job records. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain.

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_lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipIdYesIP asset ID

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 already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context beyond them: this is an off-chain read where nothing is registered, claimed, or disputed. It still does not cover behavior on an unknown ipId or the response shape, which prevents 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and efficient, but "Story Protocol (now The DATA Foundation)." is a contextless fragment that consumes space without helping the agent call the tool. The on-chain disclaimer is worthwhile, but the overall block has filler.

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 single-parameter read-only lookup with no output schema, the description states the data returned (parent capabilities and derivative job records) and the off-chain nature of the operation. Minor gaps remain around empty/unknown results and pagination, but nothing essential to correct invocation 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?

Only one parameter exists and the schema already documents it at 100% coverage ("IP asset ID"). The description's phrase "for an asset" only loosely ties ipId to the asset concept, adding no format, sourcing, or validation detail 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?

"Get the IP lineage ... for an asset: parent capabilities and derivative job records" gives a specific verb, resource, and the exact contents returned, so an agent knows what it retrieves. The opaque acronym "PCC" and lack of contrast with a potentially overlapping sibling (e.g. get_composition) keep it from 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 Guidelines3/5

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

Usage is only implied: the tool is for looking up recorded lineage for a given IP asset. There is no explicit when-to-use/when-not-to-use statement and no routing to alternatives such as get_composition or get_capability_ip, leaving the agent to infer the choice.

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.