Skip to main content
Glama

check_report_status

Read-only

Poll the status of an asynchronous KYB or adverse-media report submitted via kyb_run_submit, and retrieve a compact summary once it completes.

Instructions

Poll the status of an async report submitted via kyb_run_submit.

    Returns a compact summary of the report when status='completed'.
    Reports usually complete in about 2 minutes, up to about 4. Free (no charge).

    Args:
        run_id: The run_id returned by kyb_run_submit
        agent_type: One of "kyb-diligence", "adverse-media"
    

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": {
      "run_id": "<run_id>"
    },
    "name": "check_report_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
agent_typeNokyb-diligence

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: asynchronous timing expectations, that a 'compact summary' is returned only at status='completed', and that calls are free of charge.

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?

Key facts (what it polls, what it returns, timing, cost) are front-loaded in the first lines, with parameters last in a conventional docstring form. The Args block indentation is slightly noisy but no sentence is filler.

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?

For a simple two-parameter read tool with an output schema, this covers purpose, provenance of the identifier, timing, and cost. The main omission is an enumeration of possible status values, which would help an agent interpret results and decide whether to keep polling.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry parameter meaning, and it does: run_id is identified as the identifier returned by kyb_run_submit and agent_type's allowed values (kyb-diligence, adverse-media) are supplied even though the schema declares no enum. It stops short of explaining the run_id format, the agent_type default, or what happens if agent_type mismatches the original submission.

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 (poll) and resource (status of an async report) and anchors it to the originating sibling, kyb_run_submit, so it is clearly distinct from the submission and other lookup tools.

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?

Implies the correct workflow — call this only after kyb_run_submit and repeatedly until complete — and gives timing expectations (about 2 minutes, up to 4) that inform polling cadence. It does not explicitly say what to do on non-completed or failed statuses, nor how frequently to poll.

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