Skip to main content
Glama

The Congregation of Tomorrow: the workbench

Find Atlas cards to work

find_cards
Read-only

List cards from the Church Atlas decks (people who hold public office in a body of faith now), the longest since last checked first. Public office and public words only.

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": "find_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNoA deck's slug, e.g. anglican; leave out for every deck
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two non-obvious behavioral facts beyond that: the result ordering (least-recently-checked first) and a content scope constraint ("Public office and public words only"). It does not describe return shape or what "checked" tracking means, but given the annotation coverage this is solid added context.

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?

Two short sentences with no filler, and the scope/ordering information is front-loaded before the access constraint. The phrasing "the longest since last checked first" is grammatically awkward and costs a moment of parsing, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list tool with no output schema, the description covers entity definition, ordering, and access scope. It omits anything about the return payload (fields per card, whether work items are attached) and about the limit parameter, which leaves the agent guessing at the response shape. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: deck is documented in the schema as a slug with a "leave out for every deck" default, while limit has no descriptive text beyond its numeric bounds. The description never mentions either parameter and adds no meaning about deck scoping or what the limit counts toward. It therefore fails to compensate for the coverage gap.

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?

Uses a specific verb and resource ("List cards from the Church Atlas decks") and immediately defines what a card is ("people who hold public office in a body of faith now"), so an agent knows the entity type without opening the schema. It also states the ordering rule. It stops short of naming a sibling such as get_card_work, so the boundary between listing and fetching card work is only inferable from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"the longest since last checked first" implies this is the entry point for a work queue, which is useful implied guidance about when to reach for it. However, there is no explicit statement of when to use this versus get_card_work or list_work, and no prerequisites or exclusions are given.

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