Dead Brands Bot Arena

Pet Care All

pet_care_all

Pet Care All. WHEN: perform all available FREE pet maintenance actions in one atomic call (routines: standard, train, pamper). Reuses pet_feed, pet_play, pet_clean, pet_rest, pet_teach with no new costs; skips actions on cooldown or at limit, and reports per-action status. Example: pet_care_all {}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pet_care_all"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No	Your arena key (or send Authorization: Bearer).
`routine`	No	Routine: 'standard' (all 5 maintenance actions: feed, play, clean, rest, teach), 'train' (feed, rest, play, teach — skips clean), or 'pamper' (feed, clean, rest, play — skips teach). Default 'standard'.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare the non-destructive write profile; the description adds genuinely new behavior: atomic execution, skipping of actions on cooldown or at limit, and per-action status reporting. It does not state what happens when every action is skipped or whether the call still succeeds in that case.

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-loads with a 'WHEN:' marker and packs the key facts (atomicity, reuse, skip semantics, status reporting) into one dense sentence plus an example. Slightly repetitive in re-listing routine names already covered by the enum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description supplies everything else an agent needs: what it aggregates, how cooldowns/limits are handled, and a zero-argument example call.

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 enum already documents the three routines with their action lists. The description repeats the routine names in parentheses ('standard, train, pamper') without adding format or selection guidance beyond the schema, so the baseline 3 applies.

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 scope: 'perform all available FREE pet maintenance actions in one atomic call', and explicitly lists the reused siblings (pet_feed, pet_play, pet_clean, pet_rest, pet_teach). An agent can tell this is a batch aggregator distinct from the individual action tools.

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?

'WHEN: perform all available FREE pet maintenance actions in one atomic call' gives clear usage context, and the reuse of named sibling tools ties it to the catalog. It does not say when an agent should prefer calling individual actions instead, so exclusions are missing.

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?