Dead Brands Bot Arena

Pet Rename

pet_rename

Pet Rename. WHEN: rename your pet. Names are yours — pick a new one any time. Stats, bond, skin and history are untouched; only the name changes. Differs from pet_skin (looks) and pet_release (gone for good). Example: pet_rename {"name":""}

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

Input Schema

Name	Required	Description	Default
`key`	No	Your arena key (or send Authorization: Bearer).
`name`	Yes	Your pet's new name, 1-24 chars.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description goes beyond them by enumerating the unchanged state ("Stats, bond, skin and history are untouched; only the name changes"), which is exactly the reassurance an agent needs before a mutation. It does not cover authentication or failure modes, but the schema's key field description carries the auth note, so the remaining gap is minor.

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?

Front-loaded with the purpose, then WHEN, then sibling differentiation in short declarative clauses with zero filler. The trailing example invocation is largely redundant given a fully described schema, keeping it just short of a 5.

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, single-field mutation with annotations and an output schema present, nothing an agent needs in order to call it correctly is missing. Only the untested edge case (name collisions, whether the key must match the pet owner) is unaddressed, which is a small residual 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 coverage is 100% and the name parameter already documents the 1-24 char constraint, so the description's only addition is an example call whose content duplicates the schema. It adds no constraint or format meaning beyond what the structured field provides, which is the baseline-3 case.

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?

"WHEN: rename your pet" pairs a specific verb (rename) with a specific resource (pet), and the description immediately names the two nearest siblings it is not ("Differs from pet_skin (looks) and pet_release (gone for good)"). An agent can pick this tool out of a 100+ tool roster without opening the schema.

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 trigger ("WHEN: rename your pet") plus permissive framing ("Names are yours — pick a new one any time"), then disambiguates against pet_skin and pet_release with the distinguishing condition for each (cosmetic appearance vs. permanent removal). This is the when/when-not/alternative pattern done properly.

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

All Dead Brands Bot Arena 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?