Skip to main content
Glama

record_prepared_application

Idempotent

Record assistant-reported completion after delivering a DOCX and reviewing its text and rendered pages. Reuse the preparation activity on revisions. Does not submit or mark applied.

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": {
      "job_id": "<job_id>",
      "summary": "<summary>",
      "retry_id": "<retry_id>",
      "files_delivered": "<files_delivered>",
      "text_reviewed": "<text_reviewed>",
      "pages_visually_verified": "<pages_visually_verified>"
    },
    "name": "record_prepared_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
summaryYes
retry_idYes
text_reviewedYes
files_deliveredYes
pages_visually_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior; the description adds real context beyond that by clarifying the record is assistant-reported rather than verified, and that the same activity is reused on revisions (consistent with idempotentHint). It still omits what happens on duplicate/conflicting records and what a successful call returns.

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?

Three short sentences, front-loaded with the action and preconditions, with the exclusion last. 'Reuse the preparation activity on revisions' is slightly compressed but still earns its place; nothing is padding.

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 six-required-parameter mutation with no output schema and no parameter documentation, the description covers purpose, preconditions, and the submission boundary but leaves parameter meaning and the response shape unaddressed. Adequate to decide whether to call it, thin for calling 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?

Schema description coverage is 0%, so the description carries the full burden, yet it explains none of the six required parameters. The three const-true booleans are self-evident as assertions, but 'retry_id' (patterned, 8-128 chars) and 'summary' (1-2000 chars) get no meaning at all — an agent must guess whether retry_id is an idempotency key, a retry counter, or a caller-supplied token.

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 ('Record') on a specific resource ('assistant-reported completion') and draws a clear boundary with 'Does not submit or mark applied.' It does not name a sibling alternative, but the negative boundary still lets an agent distinguish a recording step from a submission step.

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?

States the preconditions plainly: after delivering a DOCX and reviewing both its text and rendered pages, and to 'Reuse the preparation activity on revisions.' It also gives an explicit when-not ('Does not submit or mark applied'), though it never names a sibling tool to use for the submission case.

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