Agentic Finance Graph

An agent's record

agent_record

Read-onlyIdempotent

The free record of one ranked agent: rank with evidence, bindings, and its 25 newest payments with counterparties. Unranked ids return not found: an agent never seen paying has no record to sell or show.

Input Schema

Name	Required	Description	Default
`id`	Yes	Token id, slug or wallet address

Output Schema

Name	Required	Description
`url`	No
`note`	No
`agent`	No	The record: rank with evidence, bindings, the 25 newest payments
`as_of`	No
`ranked`	No	false when the id is not among ranked agents

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agent": {
+      "description": "The record: rank with evidence, bindings, the 25 newest payments",
+      "type": "object"
+    },
+    "as_of": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "ranked": {
+      "description": "false when the id is not among ranked agents",
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile. The description adds real behavioral context on top: the exact content returned (rank, evidence, bindings, 25 newest payments) and the failure mode for unranked ids, which an agent needs to interpret an empty response correctly.

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?

Two sentences, front-loaded with the resource and its contents, then the failure condition. Tight overall, though the closing 'to sell or show' is stylistic flourish rather than actionable information.

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?

With an output schema present, the description is not obligated to explain return values, and it still summarizes the payload plus the not-found case. Annotations carry the safety profile, so nothing essential is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and the single id parameter already documents accepted forms (token id, slug, wallet address). The description supplies an additional constraint the schema does not encode: the id must correspond to a ranked agent, otherwise the call returns not found.

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 names a specific resource with a precise scope: one ranked agent's rank with evidence, bindings, and its 25 newest payments with counterparties. The 'free' qualifier implicitly distinguishes it from paid siblings like evidence_pack_quote, but no sibling is named outright, so differentiation is left partly to inference.

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 rather than stated: it tells you the tool returns 'not found' for unranked ids, which implicitly tells an agent when this call will succeed. However, there is no explicit guidance on when to choose this over find_agent, agent_statement, or evidence_pack_quote.

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

All Agentic Finance Graph tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.