Skip to main content
Glama

completion_check

DestructiveIdempotent

Verify original deliverables against current files and recorded scientific checks, and keep tasks open when required outputs are missing.

Instructions

Check original deliverables against non-stale files and recorded scientific checks. Missing outputs keep the task open.

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": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "op_id": "<op_id>"
    },
    "name": "completion_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, so the description should clarify what is mutated or destroyed. It adds one behavioral consequence—missing outputs keep the task open—but does not disclose what destructive action occurs, what permissions are needed, or what side effects the agent should expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is two tight sentences with no filler. The purpose is front-loaded and the second sentence adds a distinct behavioral consequence rather than repeating the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. However, for a destructive four-parameter tool with 0% schema description coverage, the description omits parameter meaning and mutation details that an agent needs in order to invoke it safely.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters, and the description never mentions task_id, revision, op_id, or token. The agent receives no meaning for any parameter beyond the bare names in the schema.

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 gives a specific verb and resource: check original deliverables against non-stale files and recorded scientific checks. The scope is clear enough for an agent to understand the operation, though it does not explicitly differentiate this tool from sibling check tools.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative among the many check-related siblings. 'Missing outputs keep the task open' describes an outcome, not selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.