The decks — curated card SETS, both by-situation (need decks, frontloaded for a moment of need like 'when the power goes out') and by-domain. Each with a live card count; need: true marks a situation deck.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful context about deck categorization and the `need: true` flag, but it does not explicitly confirm the operation is read-only, describe the return payload, or mention any pagination, sorting, or authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description packs a significant amount of information into two sentences. While the first sentence is somewhat awkwardly phrased ('The decks — curated card SETS'), it remains concise and avoids filler, with each clause contributing useful detail about deck types and attributes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with no output schema, the description provides adequate context about the data model, including the two deck categories and the meaning of `need: true`. It does not explicitly state that the tool returns all decks, but given the tool name and the nature of the description, this is reasonably clear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema is fully described. The description adds valuable contextual meaning beyond the schema by explaining that decks are categorized by situation or domain and that `need: true` marks situation decks, which helps the agent interpret the data even though there are no parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource ('decks') and explains that these are curated card sets with two specific types (by-situation and by-domain), which adds helpful distinction. However, it lacks an explicit verb such as 'list' or 'get', so the tool's action is implied rather than clearly stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus related sibling tools like deck_open, cards_browse, or cards_stats. There are no alternative suggestions, exclusions, or prerequisites mentioned, leaving the agent to infer the appropriate usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools are near-duplicates: read_passage and resolve both fetch WEB text for a reference; word_study already includes every occurrence that word_occurrences returns; coach_next and coach_recommend both answer 'what's next.' Search/locate/cards_browse also overlap as discovery entry points, making tool selection ambiguous despite detailed descriptions.
Most names follow an object_verb snake_case pattern (cards_browse, study_create, seal_fetch), but there are many bare verbs/nouns (ask, audit, resolve, verify, canon, harmony) and inconsistent singular/plural pairs (card_get vs cards_browse, group_create vs groups_list, want_open vs wants_list). No camelCase, but the convention is not uniform.
86 tools is an extreme count for any single MCP server, far beyond the 3-15 well-scoped range; even a broad platform would be hard for an agent to navigate. Many tools belong to unrelated subdomains (coach, steward, mesh, calendar), making the surface unwieldy.
The want/offer flow has no accept/close tool, so an agent can open a want and offer a source but never see it resolved. Group and calendar coverage are one-directional (create/join only; no leave/delete/list/update), and there is no badge listing or way to update a study group. Core reading/verification/shelf flows are solid, but lifecycle gaps remain.