Skip to main content
Glama

Agent credit

agent_credit
Read-onlyIdempotent

Machine Credit Bureau (300-950 autonomous AI agent credit & trust score): fuses Veritas Proof-of-Execution history and live domain hygiene to return an Ed25519-signed AgentCreditReport with directly pluggable agent-firewall spend limits (maxTxUsd, dailyCapUsd, humanApproveOverUsd, escrowCollateralPct). Free explorer: https://apexfaucet.xyz/veritas/ . $0.005 per call over x402 or X-API-Key.

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": {
      "agentId": "<agentId>"
    },
    "name": "agent_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesAI agent ID, wallet address, or public domain to score.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context: the report is cryptographically signed, the spend limits are directly pluggable into an agent firewall, and calls cost $0.005 via x402 or an X-API-Key. However, it never says what happens on an unscored agent, how stale or partial data is handled, or what the signature covers.

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 key facts are front-loaded, but the text is a dense run-on that bundles purpose, output fields, a free-explorer URL, and pricing into one block. The explorer link and promotional phrasing do not help an agent decide or invoke correctly, and the enumerated field list would read better as separate structure.

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?

Because there is no output schema, the description has to carry the return shape; it does mention the signed report and four spend-limit fields, which partly covers that. Still missing are score interpretation beyond the 300-950 range, error or no-history cases, and any pagination or caching behavior for a paid, idempotent call.

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%, so both parameters are already documented in the schema, making 3 the baseline. The description adds only contextual meaning for 'payment' by naming x402 and the per-call price, and does not clarify how wallet address versus domain resolution differs for agentId.

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 concrete verb and resource: it returns an Ed25519-signed AgentCreditReport, an agent credit/trust score on a 300-950 scale, and lists the concrete output fields (maxTxUsd, dailyCapUsd, humanApproveOverUsd, escrowCollateralPct). It is clearly a scoring/report tool, but it never distinguishes itself from adjacent siblings such as agent_card_grade or work_grade, so an agent must infer the boundary.

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?

Reads as a scoring endpoint for an agent ID, wallet, or domain, so the usage context is implied rather than stated. There is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives like agent_card_grade, and no stated preconditions beyond a required agentId.

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.

Resources