Skip to main content
Glama

process_status

Is this company done, and what next (ZEN-2). Start and end here.

done: no held AI proposal, no unmatched or partly matched bank movement, Suspense explained, no unreadable, waiting, unreviewed or rejected-unbooked document (null when it cannot be checked). Lists every open item; work them through book_documents_act or reconcile_bank_act as each row's process says. Read-only.

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": {
      "company_id": "<company_id>"
    },
    "name": "process_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
company_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden and does set the safety profile itself: it states the tool is read-only and explains that the `done` flag can be `null` when a condition cannot be checked, which is a useful edge case. It also discloses that the tool lists every open item and that each row self-describes its next action. However, it does not disclose pagination behavior, which matters for a listing tool with a default of 20 and a cap of 100 — an agent could easily assume it received the complete list.

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 leads with the core question an agent would ask, then defines the `done` predicate in one dense clause and closes with the routing instruction. The trailing 'Read-only.' is well placed; the '(ZEN-2)' ticket reference is the only element that fails to earn its space.

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 read-only status tool with no output schema, the description does good work explaining what is checked and what each returned row contains (`process`). The omission is pagination: with 3 parameters at 0% schema coverage and a hard cap of 100 rows, the description's claim to list 'every open item' leaves the agent unable to know whether the results are complete or truncated.

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 description coverage is 0%, so the description should compensate for three undocumented parameters, yet it mentions none of them — not company_id, and not limit/offset. Worse, 'Lists every open item' implies an unbounded complete listing, which is at odds with the limit/offset pagination the schema actually exposes.

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 states what the tool answers ('Is this company done, and what next') and precisely enumerates the conditions that make a company 'done' (no held proposal, no unmatched bank movement, suspense explained, no unreadable/unreviewed documents). It is clearly a readiness-check tool rather than a mutation tool, and it names book_documents_act and reconcile_bank_act as the tools that resolve the listed items, distinguishing it from them.

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

Usage Guidelines4/5

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

'Start and end here' explicitly frames this as the entry and exit point of a workflow, and the description tells the agent to work each returned row through book_documents_act or reconcile_bank_act according to that row's `process` value. There is no explicit when-not guidance, but the routing instruction is unusually concrete.

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