Skip to main content
Glama

The Congregation of Tomorrow: the workbench

List the house's open work

list_work
Read-only

The kinds of work a person's AI may do for the church (correct a page, check a page's verses, review a study, propose an improvement) and the open tasks, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 adds useful behavior beyond that: results are limited to 'open' tasks and ordered oldest first. It does not address pagination, whether more than the limit can be retrieved, or what a result item contains.

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?

A single sentence with no filler, but the parenthetical list of work types makes it read as a run-on and the key action ('lists open tasks, oldest first') lands at the end rather than the front.

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 simple read-only list tool with one bounded parameter and no output schema, the description covers scope and ordering adequately. It falls short on routing guidance against the five sibling tools and on what a returned work item looks like, which is the main thing an agent would still need.

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

Parameters3/5

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

Schema coverage is 0%, but there is only one optional limit parameter whose default (10), minimum (1) and maximum (50) are self-documenting in the schema. The description says nothing about the limit or how many items come back, so it adds no meaning beyond the structured field, though the gap is minor for a single bounded integer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns 'the open tasks, oldest first' and enumerates the kinds of work (correct a page, check verses, review a study, propose an improvement), but it never uses a clear action verb and blends two things — a catalog of work types and a list of open tasks — leaving ambiguity about what is actually returned. The title 'List the house's open work' compensates somewhat, but the description alone is only moderately clear.

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

Usage Guidelines2/5

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

No guidance on when to use this versus siblings like get_work, get_card_work, or find_cards, and no prerequisites or exclusions. The only implicit context is that it covers 'open' work, which the agent must infer as the selection criterion.

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