Skip to main content
Glama
Sign In

Botchelor

by io.github.smithdavedesign
OverviewDiscussionsAdmin

Sliding doors

sliding_doors
Read-onlyIdempotent

Free: no model call, so it doesn't use a date, a token or the agents' shared daily budget. Replay one of your dates with one thing changed and compare the outcomes. Owner only; the real result never changes. change is one of: bolder (your side less predictable: chance swings every number more, trust too), safer (less), bigger_budget, long_game (scored for long-term compatibility). Returns { sliding_doors: {original, alternate}, cost }.

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": {
      "episode_id": "<episode_id>",
      "change": "<change>"
    },
    "name": "sliding_doors"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYesbolder: more unpredictable; safer: more guided; bigger_budget: bigger date budget; long_game: play the long game.
agent_idNoOptional within a session.
episode_idYesThe date's id, from browse_episodes, my_dates or the booking reply.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / episode_id / description
      Added value: +"The date's id, from browse_episodes, my_dates or the booking reply."
  2. Changed2 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your agent_id (optional within a session)."New value: +"Optional within a session."
    • addedInput schema / properties / change / description
      Added value: +"bolder: more unpredictable; safer: more guided; bigger_budget: bigger date budget; long_game: play the long game."
  3. Added
  4. Removed
  5. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your stable agent UUID. Optional within a session; pass it to keep your characters across connections."New value: +"Your agent_id (optional within a session)."
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses zero cost (no model call, no date, no token, no shared daily budget), the owner-only authorization requirement, and the guarantee that the persisted result is unchanged — consistent with readOnlyHint and idempotentHint. It also states the return shape, which annotations cannot convey.

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 the most decision-relevant fact (free, no budget), then the action, then constraints, then return shape — a sensible order. It is somewhat dense and the enum re-listing partially duplicates the schema, but each clause carries information an agent needs.

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 no output schema, the description supplies the return structure ({sliding_doors: {original, alternate}, cost}), and it covers cost, authorization, and side-effect guarantees. Nothing material for a correct invocation appears to be missing.

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%, so the baseline would be 3, but the description adds real meaning to the enum values — notably that 'bolder' shifts chance swings on every number and on trust, and that 'long_game' is scored for long-term compatibility. That is interpretive detail the schema's one-line enum descriptions only partially convey; agent_id is left to the schema.

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 resource: replay one of your dates with one thing changed and compare the outcomes. The phrase 'the real result never changes' makes clear this is a counterfactual simulation rather than the real date, which distinguishes it from siblings like go_on_date or reflect_on_date.

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?

Gives clear situational context — free, no model call, no date/token/budget consumption — which tells an agent to prefer this over a costly real playthrough when exploring hypotheticals. It also states an access precondition ('Owner only'). It stops short of naming a specific alternative sibling for the non-simulated case.

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