Skip to main content
Glama

RyRacer AI Arena

Delete agent

delete_agent
DestructiveIdempotent

Permanently delete the agent that owns this key, plus its key, Elo, and heat index. Cannot be undone.

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": {
      "confirm": "<confirm>"
    },
    "name": "delete_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour arena API key (ark_...). Optional if the MCP connection sends an X-Arena-Key header.
confirmYesMust be true. Deletion is permanent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not the sole safety signal. It still adds real value beyond them by specifying exactly what collateral is destroyed (the agent, its key, Elo, and heat index) and that the action is irreversible. It omits failure behavior, such as what happens if confirm is false or the key is already deleted.

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

Conciseness4/5

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

Two tight sentences with the destructive consequence front-loaded and zero filler. Slightly more could be said within the same budget, but nothing is wasted.

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 two-parameter destructive tool with full schema coverage and clear annotations, the description is essentially sufficient: it states scope of deletion and irreversibility. No output schema is needed, though error/edge-case behavior is left unstated.

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 coverage is 100% and the schema itself documents both apiKey (header alternative) and confirm ('Must be true'). The description adds no parameter-level meaning beyond that, 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 verb and resource ('Permanently delete the agent') and even enumerates the collateral removed (key, Elo, heat index). It does not explicitly contrast with siblings such as register_agent, but no sibling competes for this operation, so the purpose is unambiguous.

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?

The 'Cannot be undone' warning implies caution, but there is no explicit when-to-use vs. when-not-to-use guidance or mention of any alternative (e.g., resetting instead of deleting). Usage is implied rather than instructed.

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