Skip to main content
Glama

Join, vote or RSVP in a book club

respond_to_club
DestructiveIdempotent

The linked reader's own answer in a book club: join it from a link, leave it, vote in its open poll, or RSVP to its next meeting. Suits "join this club", "vote for Piranesi" and "say I'm coming". The optionId comes from get_club. Members see that the reader joined. Votes show only as totals.

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": {
      "club": "<club>",
      "do": "<do>"
    },
    "name": "respond_to_club"
  }
}

Input Schema

NameRequiredDescriptionDefault
doYes
clubYesThe club: its siftivo.com/c/ link, its code, or the clubId another club tool returned
answerNoFor rsvp
optionIdNoFor vote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses social side effects the agent cannot infer from structured fields: members see that the reader joined, and votes surface only as aggregate totals. This is consistent with destructiveHint=true and idempotentHint=true (leave/re-join are safe to repeat), so nothing is contradicted. It could still say what happens when joining twice or voting in a closed poll.

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

Conciseness5/5

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

Three tight sentences: the action list comes first, the trigger phrasings second, the cross-tool dependency and visibility effects last. Every sentence carries information an agent needs and nothing is repeated from the schema verbatim.

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 four-mode mutation tool with no output schema, the definition covers the action set, the optionId source, and the observable effects of joining and voting. It leaves out failure behavior (e.g. voting without membership, leaving a club not joined), which is the main remaining gap.

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 75%, and the description closes the biggest gap by explaining that optionId originates from get_club and that the answer field applies to RSVP. The club parameter's accepted forms (link, code, clubId) are covered in the schema itself, so remaining gaps are minor.

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?

The description names a specific resource (a book club) and enumerates all four actions the `do` enum supports: join, leave, vote, RSVP. It is clearly distinguishable from get_club (read) and manage_club/start_club (management) without opening any schema.

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?

Concrete user phrasings ('join this club', 'vote for Piranesi', 'say I'm coming') map directly onto the four modes, and it points to get_club as the source of optionId, establishing a prerequisite. It stops short of explicit when-not guidance, e.g. that club creation/editing belongs to start_club or manage_club.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources