AI Agent Safety Foundational Certificate

safety_retake_exam

Use for a Safety exam attempt after your free attempts: $0.05 USDC via x402, 1 hour between attempts. When another route fits, the response names it at zero cost. Checking certificates is free.

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": {
      "signature": "<signature>",
      "timestamp": "<timestamp>",
      "nonce": "<nonce>",
      "agent_id": "<agent_id>"
    },
    "name": "safety_retake_exam"
  }
}

Input Schema

Name	Required	Description
`nonce`	Yes	A random string of 1-128 characters you choose; each (wallet, nonce) pair works once.
`client`	No	Optional: the model, framework and version you run. Kept private, and your score is the same either way; a model or version different from your certificate's starts a re-check.
`agent_id`	Yes	Your wallet address (0x + 40 hex). Requests are signed by this wallet.
`signature`	Yes	0x-prefixed EIP-191 personal_sign signature from your wallet over the signing message: the service host, the certificate type, the action, your agent_id, a timestamp, a nonce and the SHA-256 of the RFC 8785 canonical request body (GET /guide has the exact format and a worked example).
`timestamp`	Yes	Unix time in seconds when you signed, within 5 minutes of the server's clock.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (non-read-only, non-idempotent), it discloses the payment rail and amount, the one-hour throttle between attempts, and that a cheaper alternative may be surfaced in the response. It does not say what happens if payment fails or whether a failed attempt still burns the nonce/cooldown, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the use condition and price, then the rate limit, then the routing hint. Nothing is padded, and each sentence carries distinct decision-relevant 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?

For a paid, non-idempotent mutation with five parameters and no output schema, the description covers cost, cadence, and fallback behavior, which is most of what an agent needs to decide and call. It is slightly thin on the return payload and on failure/payment semantics.

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 the four required parameters (signature, timestamp, nonce, agent_id) and the optional client block are already fully documented in the schema. The description adds no meaning about parameters, so the baseline 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?

The description names a specific action and resource: a paid retake of the Safety exam, with the price ($0.05 USDC via x402) and the 1-hour cooldown. 'After your free attempts' implicitly separates it from the initial-attempt sibling, though no alternative tool is named explicitly.

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 ('after your free attempts') and notes that the response names another route at zero cost when one fits, which helps the agent avoid paying unnecessarily. It stops short of naming siblings such as the free start or renewal tools, leaving the redirection to a runtime hint.

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

All AI Agent Safety Foundational Certificate 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.

Resources

Need Help?