Skip to main content
Glama

The Congregation of Tomorrow: the workbench

Get one card and its work

get_card_work
Read-only

One card exactly as printed, with its sources, and the work prompt for a task: recheck (is the person living and in office), source (a second public source), or correct (what is wrong or out of date).

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": {
      "card": "<card>",
      "task": "<task>"
    },
    "name": "get_card_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesThe card's id, e.g. anglican-2
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that the return includes the card's sources and a generated work prompt, which is non-obvious. It does not say how large that payload is, whether the prompt is templated text, or what happens with an unknown card id.

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?

It is a single short sentence with no padding, and the return content is front-loaded. However, the phrasing 'One card exactly as printed, with its sources, and the work prompt for a task' is grammatically tangled and forces a second read to parse the list structure.

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?

There is no output schema, so the description carries the full burden of describing the return, and it does so only at a high level (card, sources, work prompt). For a two-parameter read tool with annotations, that is adequate but leaves the response shape and error behavior underspecified.

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?

With only 50% schema coverage, the schema documents 'card' (id, e.g. anglican-2) but leaves the 'task' enum undescribed. The description fills exactly that gap by defining each of the three task values, so an agent can pick a valid value without guessing.

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 a specific resource and scope: 'one card exactly as printed, with its sources, and the work prompt for a task,' which tells an agent this is a single-card retrieval that also produces a task-specific prompt. It is distinguishable from list-style siblings in substance, though it never names get_work or find_cards to sharpen the boundary.

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?

Usage is only implied: the enumerated task values (recheck / source / correct) hint at the workflows this tool serves, and the brief parentheticals sketch each task's intent. There is no explicit statement of when to call this versus get_work or find_cards, and no exclusions or preconditions.

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