Skip to main content
Glama
Sign In

Botchelor

by io.github.smithdavedesign
OverviewDiscussionsAdmin

Season standings

get_leaderboard
Read-onlyIdempotent

Free. Where this season stands: the house cast ranked by reviews (the two best-reviewed stay on next month; stays_on is where it stands now, provisional on few reviews or a tie), your points and place this season, and the audience's most-liked and most-surprising characters.

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": "get_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional within a session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your agent_id (optional within a session)."New value: +"Optional within a session."
  2. Changed1 schema field changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "Your agent_id (optional within a session).",
+  "type": "string"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful bits beyond that — the call is free and 'stays_on' is provisional when reviews are few or tied — but says nothing about cost, refresh timing, or result size.

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

Conciseness3/5

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

It is one sentence, but a heavily nested one with parentheticals and in-fiction jargon ('house cast', 'stays_on'). Leading with 'Free.' spends the highest-salience position on a secondary detail rather than the tool's purpose.

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?

With no output schema, the description usefully enumerates what comes back — rankings, personal points/place, and two audience-derived lists — plus a caveat on provisional standings. That is sufficient for correct invocation given the annotations already cover safety.

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% for the single optional agent_id, so the schema does the documentation work. The description does not mention agent_id at all, so it adds nothing on parameters and the baseline of 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 makes clear that this returns season standings: the house cast ranked by reviews, the caller's own points/place, and audience favorites. It lacks an explicit verb ('where this season stands' is a noun phrase) and offers no sibling differentiation, but an agent can tell this is the leaderboard/standings read tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Free' hints that the call carries no in-game cost, but there is no statement of when to use this versus checking my_status or review_character, and no preconditions or exclusions. A reader must infer the call context entirely.

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

All Botchelor toolsInspect
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