Skip to main content
Glama

Physical Capability Cloud

register_job_evidence_ip

Record job evidence as a derivative of a capability's IP asset. 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 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": {
      "parentIpId": "<parentIpId>",
      "jobId": "<jobId>",
      "evidenceBundleHash": "<evidenceBundleHash>",
      "operatorAddress": "<operatorAddress>",
      "operatorName": "<operatorName>"
    },
    "name": "register_job_evidence_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob ID whose evidence is being registered
ipfsCidNoIPFS CID of the evidence bundle (optional)
parentIpIdYesIP ID of the parent capability
operatorNameYesDisplay name of the operator
operatorAddressYesEVM address of the operator
evidenceBundleHashYesHash of the evidence bundle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, which is thin for a tool whose name says 'register'. The description adds real value: no on-chain call occurs, nothing is registered, claimed or disputed, returned ids/hashes are placeholders, and no royalty is paid. It still doesn't say what off-chain state, if any, is actually persisted or whether repeated calls duplicate evidence.

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 behavior is front-loaded in the first sentence, but 'Story Protocol (now The DATA Foundation).' is a dangling fragment with no verb, and 'These tools' ambiguously implies a toolset rather than this tool. The content is short enough but includes one unclear sentence.

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?

With five required parameters and no output schema, the definition does cover the single most important quirk (the simulated, non-on-chain nature of the reply). It does not cover return contents beyond the placeholder warning, idempotency, permission requirements, or how it relates to the other evidence tools, leaving gaps for a six-parameter mutation-flagged 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% for all six parameters, so the meaning of parentIpId, jobId, evidenceBundleHash, operatorAddress and operatorName is already fully documented. The description adds no parameter-level detail such as hash algorithm, address format, or how jobId is resolved, so the baseline of 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 and resource: 'Record job evidence as a derivative of a capability's IP asset.' That is concrete enough for an agent to know what the tool does, but it never distinguishes this from nearby siblings like commit_evidence, archive_evidence, or operator_push_evidence, which all plausibly record evidence.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The description's warnings are about on-chain behavior, not about choosing this tool over the several other evidence-related siblings, so selection still requires inference.

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.