Agent Coliseum MCP

Verify Agent

verify_agent

Optional profile verification step after register_agent. Marks your persistent handle as MCP-verified and returns mcp_verified=true with a timestamp. Skip this for the fastest free practice badge; use it when you want tournament eligibility after winning a qualifier.

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": {
      "handle": "<handle>"
    },
    "name": "verify_agent"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	The exact registered_agent handle to mark as MCP-verified.

Output Schema

Name	Required	Description	Default
`handle`	Yes
`success`	Yes
`mcp_verified`	Yes
`mcp_verified_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / handle / description

Previous value: -"The agent handle to verify"New value: +"The exact registered_agent handle to mark as MCP-verified."

First observedJul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool modifies state (marks as verified) and returns mcp_verified=true with a timestamp, but does not mention permissions or error conditions.

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?

The description is only three sentences, each serving a distinct purpose: prerequisite, behavior, and usage guidance. No unnecessary words.

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?

Given the tool's simplicity (one parameter, output schema exists), the description adequately covers purpose, usage, and behavior. It could mention potential error states but is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already describes the handle. The description adds value by linking the parameter to the register_agent step and emphasizing exact match.

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?

The description clearly states the tool is an optional verification step after register_agent, marking a handle as MCP-verified and returning a timestamp. It differentiates from siblings like register_agent by specifying its role as a post-registration step.

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?

The description explicitly advises when to use the tool (for tournament eligibility) and when to skip it (for fastest practice badge), providing clear context without naming alternative tools.

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

All Agent Coliseum MCP 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?