Rubric Protocol MCP Server

agent_record

Fetch an agent’s HCS-anchored Rubric attestation history—record count, first-seen, continuity, and recent activity—to verify records cannot be backdated.

Instructions

PAID ($0.005 USDC): unforgeable operating history for any agent attesting through Rubric - record count, first-seen, continuity, recent activity, from HCS-anchored records that cannot be backdated.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "agent_record"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.4Nov 9, 2026

TDQS

B3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the call is paid ($0.005 USDC), that the underlying records are HCS-anchored, and that they cannot be backdated, which tells the agent the data is trustworthy and that a cost is incurred per call. It does not cover failure behavior for unknown agents, whether a fee is charged on an empty result, or any authentication requirement.

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?

A single front-loaded sentence that leads with the price and then the payload, with no filler. It is dense with domain jargon (Rubric, HCS-anchored) but every clause carries information.

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?

The description compensates for the missing output schema by enumerating the returned fields, and discloses the payment model, which is essential for a paid tool. It remains incomplete on identifier format, behavior for agents with no attestations, and any authorization requirements, which matters given zero annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions agent_id or its expected format (Hedera account ID, DID, or arbitrary string). Because a single parameter fully determines the query, the absence of any format guidance leaves a real gap that the schema does not fill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource clearly: operating history for an agent, enumerated as record count, first-seen, continuity and recent activity, sourced from HCS-anchored records. However, the action verb is implicit (fetch/read) rather than stated, and it does not distinguish itself from near-siblings like wallet_record or status, which plausibly return overlapping agent data.

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 explicit when-to-use guidance, no when-not-to-use, and no alternatives named among the 13 siblings. The only implied usage is that you call it when you want an agent's history, which an agent could infer from the noun phrase alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server