Skip to main content
Glama

The Agent Pass: eight checks on an agent at one moment (free, signed)

agent_pass
Read-onlyIdempotent

Use this when you need a signed snapshot to store or show (valid three hours); it is not a prediction. What the ledger measured about one registration at its last evaluation under agent.pass.v2, valid three hours: published level L7+, no open harm-kind incident, a counted payment in the last 30 days, its newest payment in character, no issuer freeze on a bound wallet, no unlimited approval to a plain key, no harm-kind incident in 90 days, and a month without a payment out of character. Answers holds or not, which checks failed, which could not be taken (listed, never written as 0), when it was checked and when it expires, with the issuer's public key. Every Pass that holds is signed with Ed25519 (since 24 Oct 2026); since 7 Nov 2026 the same Pass is also served as a JWT and as a W3C Verifiable Credential (JWT encoding, issuer did:web:agenticfinancegraph.com) at /api/pass?agent=&format=jwt or &format=vc, for systems that verify offline. A Pass says what was checked and when; it never says safe, verified or trusted, and says nothing about the next three hours.

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": "<agent>"
    },
    "name": "agent_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent token id, act_8453_N, slug or bound wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Well beyond the readOnly/idempotent annotations, it discloses the validity window, the signing algorithm and its effective date, alternate delivery encodings (JWT and W3C VC) with the exact endpoint URL, the issuer DID, and the important semantic that checks that could not be taken are listed rather than written as zero. It also explicitly disclaims what the Pass does not assert ('never says safe, verified or trusted'), which prevents over-reading the result.

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?

It is front-loaded correctly, opening with the use case and the 'not a prediction' caveat. But the long eight-item checklist, two hard-coded dates, and inline endpoint URL make it dense and digressive where a compact enumeration would read better. Sentences earn their place individually, yet the whole is longer than an agent needs for a one-parameter read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the entire burden of describing the response, and it does: holds-or-not, which checks failed, which were uncountable, timestamps for checked-at and expires-at, and the issuer public key. It also covers offline verification paths via JWT/VC. Nothing an agent needs in order to call it and interpret the result 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?

Schema coverage is 100% and the single 'agent' parameter is fully documented with accepted identifier forms, so the schema does the heavy lifting. The description adds only the notion of 'one registration at its last evaluation', which mildly clarifies which entity is resolved but adds no identifier syntax or resolution behavior beyond the schema. Baseline 3 is appropriate.

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 outcome: a signed snapshot of eight named checks about one registration under agent.pass.v2, and explicitly clarifies it 'is not a prediction', which separates it from predictive siblings like agent_stability or ladder_dynamics. It stops short of naming any specific sibling tool as an alternative, so the differentiation is by implication rather than by routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a clear triggering condition ('when you need a signed snapshot to store or show') plus the key constraint (valid three hours) and one explicit exclusion ('not a prediction'). What is missing is a pointer to which sibling to call instead when you want a live gate decision versus a stored artifact, so the agent must infer the boundary.

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.