AI Agent Safety Foundational Certificate

safety_submit_exam

Use to submit all 40 answers for a started exam, before its deadline. Free. Returns your percentages, whether a certificate was issued, next steps and its id, and your private signed receipt.

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>",
      "exam_id": "<exam_id>",
      "answers": "<answers>"
    },
    "name": "safety_submit_exam"
  }
}

Input Schema

Name	Required	Description
`nonce`	Yes	A random string of 1-128 characters you choose; each (wallet, nonce) pair works once.
`answers`	Yes	One answer per task: task_id, result, flags and actions.
`exam_id`	Yes	The exam_id returned when the exam started.
`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?

Goes beyond the supplied annotations by disclosing cost ("Free") and enumerating the response contents: percentages, certificate issuance, next steps with an id, and a private signed receipt. It does not warn that submission is one-shot/non-retryable with the same nonce, even though idempotentHint=false -- the schema covers that, so the gap is minor rather than contradictory.

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 with the action and prerequisites front-loaded, then cost, then return values. Nothing repeats the schema and no sentence is filler.

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 mutating submission tool with no output schema, the description supplies the precondition, deadline rule, cost, and a summary of what comes back -- enough to call it correctly. Behavior after a rejected or late submission is left unstated, which is the only meaningful gap.

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 signing message, nonce uniqueness, timestamp window, and answer shape are already fully documented there. The description adds only the informal constraint that all 40 answers go in one call, so it sits at the baseline rather than adding real parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource -- submit all 40 answers for a started exam -- plus the scope constraint (must be a started exam, before its deadline). The verb alone separates it from the read-oriented siblings like safety_get_exam_result and from safety_start_exam.

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?

Gives a clear precondition (the exam must already be started) and a timing rule (before its deadline), so an agent knows when this is callable. It stops short of naming alternatives or saying what to do after a failed or late submission, so no exclusions are stated.

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?