Share by DeltaBreen

get_id_check

Read-only

Where one ID check stands: its status (waiting, in_progress, passed, review = needs the human's review, failed, expired, cancelled), dates and the page where the human sees the result. The result itself is locked to the human's workspace and never shown here.

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": {
      "id_check_id": "<id_check_id>"
    },
    "name": "get_id_check"
  }
}

Input Schema

Name	Required	Description	Default
`id_check_id`	Yes	The ID check's id (uuid), from create_id_check or list_id_checks.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.7/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, so the description adds real value beyond them: the specific status vocabulary (including that 'review' means a human must act), and the crucial expectation that the underlying result is workspace-locked and never returned here. No permission or pagination detail, but for a read operation that is minor.

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?

Two sentences with no filler, and the status enumeration is appropriately front-loaded since the schema carries no enums. The long parenthetical explanation of statuses is dense but earns its place as the only source of that vocabulary.

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 must carry the return shape and largely does: status, dates, and result page. 'Dates' remains vague (created, updated, expires?) and the page field's format is unstated, but an agent knows what to expect and what it will never get.

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?

Only one parameter, and its schema description already covers it fully (uuid, sourced from create_id_check or list_id_checks). The description adds no syntax or provenance detail of its own, so the baseline 3 applies.

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 names the resource (one ID check) and precisely enumerates what it returns: status, dates, and the human-facing page. 'One' implicitly contrasts with the sibling list_id_checks, though it never names that sibling and uses a noun phrase rather than a clear retrieval verb.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: checking the state of a single check whose id you already hold. The stronger routing hint — that the id comes from create_id_check or list_id_checks — lives in the schema, not the description, and no sibling or when-not condition is named.

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

All Share by DeltaBreen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?