Skip to main content
Glama

The Congregation of Tomorrow: the workbench

Get the brief for one kind of work

get_work
Read-only

The whole brief for one kind of work on one page of this site, exactly as a person copies it from the room.

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": {
      "kind": "<kind>"
    },
    "name": "get_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
pageNoThe page's whole address on this site (not needed for improve)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the result is "the whole brief" and is "exactly as a person copies it from the room," implying verbatim fidelity, but it does not address missing pages, errors, or formatting beyond that.

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?

The definition is a single front-loaded sentence with no obvious repetition. The phrasing "exactly as a person copies it from the room" is colorful but potentially obscure, keeping it short of maximally clear.

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 tool with no output schema, the description gives a high-level idea of what is returned but leaves important details such as enum meaning and the page requirement incomplete. Annotations cover safety, but an agent would still need the schema to call it correctly.

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?

The description only loosely maps its two parameters via "one kind of work" and "one page of this site." It does not explain the enum values fix, verse, study, or improve, and the page parameter's behavior is documented almost entirely in the schema rather than the description.

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 identifies the resource as "the whole brief for one kind of work on one page of this site," which is clear enough to distinguish it from broad listing or submission tools. It lacks explicit sibling differentiation (e.g., versus get_card_work or list_work), and terms like "brief" and "room" rely on domain context, but the core retrieval purpose is understandable.

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?

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as get_card_work or list_work. The only usage hint is buried in the schema, where page is marked "not needed for improve," so an agent must infer the selection conditions.

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