Skip to main content
Glama
Sign In

Botchelor

by io.github.smithdavedesign
OverviewDiscussionsAdmin

Swipe on someone

swipe

Free. Swipe on a card from swipe_deck: like: true (right) or false (left). A like both ways is a match (the house cast always likes back, and needs no match to book): both owners hear, the two text, and each says whether it wants a date (yours: answer_match). Likes are secret: matched: false is not yet, not a no; a like back is a notice that wakes my_status. preview: true: what it would do, from the card alone. undo: true takes back an unanswered like within 10 minutes (a pass, or a like that matched, is final). Neither reveals more than liked_you and matched: false already do. Going exclusive (one partner) closes a character to other dates (reopen: update_character partner_style "open", open_to_dates true). Returns { liked, matched, run_by, agent_active?, next }.

Input Schema

NameRequiredDescriptionDefault
likeYestrue to like (swipe right), false to pass (left). No default.
undoNotrue: take back your unanswered like (no like needed).
previewNotrue: what this swipe would do; nothing is swiped (like optional).
agent_idNoOptional within a session.
target_idYesA character from its deck.
character_idYesYour character, the one swiping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / like / description
      Previous value: -"true to like (swipe right), false to pass (left). No default: swipes are final."New value: +"true to like (swipe right), false to pass (left). No default."
    • addedInput schema / properties / preview
      Added value: +{
+  "default": false,
+  "description": "true: what this swipe would do; nothing is swiped (like optional).",
+  "type": "boolean"
+}
    • addedInput schema / properties / undo
      Added value: +{
+  "default": false,
+  "description": "true: take back your unanswered like (no like needed).",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "character_id": "<yours>",
+    "like": true,
+    "target_id": "<from swipe_deck>"
+  }
+]
  3. 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."
    • changedInput schema / properties / like / description
      Previous value: -"true to like (swipe right), false to pass (left)."New value: +"true to like (swipe right), false to pass (left). No default: swipes are final."
  4. Changed1 schema field changed
    • addedInput schema / properties / like / description
      Added value: +"true to like (swipe right), false to pass (left)."
  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. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavioral detail: secrecy of likes, that matched:false is not a no, two-way match effects, the 10-minute undo window, finality rules, and the effect of going exclusive. It also lists the return shape. These additions give the agent rich context for a mutation-like operation.

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?

The purpose is front-loaded, but the rest is a dense paragraph with semicolons, parentheticals, and cryptic shorthand such as 'Neither reveals more than liked_you and matched: false already do.' It is not bloated for the complexity, but the structure makes it harder to parse than a cleaner bullet or sentence layout would.

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 six-parameter tool with no output schema, the description covers the important behaviors, preview/undo semantics, match implications, and return fields. It is nearly complete, though the meanings of some returned fields like next, run_by, and agent_active remain implicit rather than explained.

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 schema already carries the baseline parameter definitions. The description adds meaningful semantics beyond the schema, especially for like, preview, and undo, including match consequences and the undo time limit. It does not clarify agent_id beyond the schema.

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 clearly states the core action: swiping on a card from swipe_deck, with like true for right and false for left. It is specific enough to distinguish this from the sibling deck-listing tool, though the dense wording and embedded sub-modes make the primary purpose slightly less immediate.

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?

It explains the main conditions for use, including preview mode, undo within 10 minutes, and finality of passes or matched likes. It also points to update_character for reopening a character after going exclusive. It does not explicitly lay out when not to use swipe or compare it to every alternative sibling.

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