Skip to main content
Glama

get_check

Read-only

Get the status of a check started with check_document. While it runs, returns the estimated time left and poll_after_seconds; when done, a summary, a disclaimer to pass on, and a link to the full report (valid 24 hours).

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": {
      "token": "<token>"
    },
    "name": "get_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the two-phase return shape (in-progress vs done), the presence of a disclaimer that must be passed on, and a 24-hour validity limit on the report link. It omits behavior on invalid or expired tokens and the units of poll_after_seconds, keeping it shy of a 5.

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?

One densely packed sentence with no filler: the two lifecycle branches are front-loaded and each clause (ETA, poll interval, summary, disclaimer, 24h link) carries distinct information.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns and does so for both lifecycle states, including the operational constraint on the report link. Error and expiry handling for the token is the notable gap.

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% for the single token parameter, so the schema itself says nothing about it. The description implies the token is the handle from check_document but never states that explicitly or that it may expire, so it only partially compensates for the coverage gap.

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

Purpose5/5

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

States a specific verb and resource (get the status of a check) and anchors it to the sibling that creates it (check_document), so an agent can distinguish this poller from the tool that starts the work.

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?

The description establishes the prerequisite flow (only valid for a check started with check_document) and gives concrete polling guidance via poll_after_seconds and estimated time left. It does not spell out an explicit stop/abandon condition, but the when-to-use context is clear.

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