AI Agent Safety Foundational Certificate

safety_renew_exam

Use to renew your Safety certificate, in the last 14 days before it expires or after it has expired: free. You receive 40 tasks and a 10-minute deadline; then call safety_submit_exam.

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_renew_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.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive call, and the description adds real context beyond that: the exam format (40 tasks), the time limit (10 minutes), and the cost (free). It does not warn that a second invocation starts a fresh exam or consumes the attempt, which matters given idempotentHint=false.

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?

A single dense sentence front-loads the purpose, then the eligibility window, cost, exam parameters and next step, with no redundant or filler wording. Every clause carries information the agent needs before calling.

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 5-parameter tool with full schema coverage and no output schema, the description covers purpose, prerequisites, timing, and the follow-up call, which is nearly everything needed. The only gap is how the 40 tasks are delivered (in this response versus a separate fetch), which an agent would have to discover itself.

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%, with each parameter (signature, timestamp, nonce, agent_id, client) documented in the schema itself, so the baseline is 3. The description adds nothing about parameters, such as the signing message contents, leaving all parameter meaning to the schema.

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?

States a specific verb and resource ('renew your Safety certificate') and names the follow-up tool safety_submit_exam, so the agent can place it in the exam flow. It does not differentiate from the similarly named safety_retake_exam or safety_start_exam peers, which remains a small ambiguity.

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

Usage Guidelines5/5

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

Gives an explicit eligibility window ('last 14 days before it expires or after it has expired'), which implicitly excludes use earlier in the certificate lifetime, and states the cost ('free'). It also routes the agent forward by naming safety_submit_exam as the next call.

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?