Skip to main content
Glama

My book clubs

get_my_clubs
Read-only

Every book club the linked reader is in, with what each is reading, when it next meets, and whether a vote, an RSVP or unread messages wait on them. Suits "what's going on with my book club?" and "do I have anything to do for book club?".

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_my_clubs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing what the payload contains, including state flags for pending votes, RSVPs and unread messages, and by noting the scope is tied to 'the linked reader' (an authenticated context). It says nothing about result size, ordering, or empty-club behavior, but with annotations carrying the safety burden that gap is minor.

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?

Two sentences, both earning their place: the first front-loads the scope and the content of the result, the second supplies usage signals via example user questions. No repetition of the title, no filler, and the most decision-relevant information comes first.

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?

There is no output schema, so the description has to sketch the return shape, and it does so by listing the per-club fields an agent will receive. Combined with a zero-parameter schema and annotations covering safety, an agent has essentially everything needed to call and interpret the result. Ordering and volume of results remain unspecified, which keeps it from a 5.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies no filtering arguments are required, which matches the empty input 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 names the resource and its scope precisely: 'Every book club the linked reader is in', which distinguishes it from the singular get_club and from mutation siblings like manage_club or respond_to_club. It also enumerates what each entry carries (current read, next meeting, pending vote/RSVP/unread). It stops short of explicitly naming the sibling tools, so the differentiation is implied rather than stated.

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?

Two concrete example questions ('what's going on with my book club?' and 'do I have anything to do for book club?') give clear intent-based guidance on when to reach for this tool. There is no explicit exclusion or pointer to alternatives such as get_club for a single club or respond_to_club when the user wants to act, leaving the routing partly inferential.

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