Skip to main content
Glama

Cybercentry B20 Token Verification

get_verification_report

Fetch the report for a jobId returned by verify_b20_token. Free to call. While the scan is still running this returns status 'running' with a retryAfter in seconds — wait that long before calling again.

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": {
      "jobId": "<jobId>"
    },
    "name": "get_verification_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId returned by verify_b20_token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals the tool is free (cost), that the operation is asynchronous with a 'running' state and a retryAfter hint, which is exactly the behavior an agent needs to avoid hot-polling. It omits terminal states other than implicitly completing and says nothing about failure or expiry handling.

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?

Three short sentences, front-loaded with the purpose, then cost, then the polling rule. Nothing is wasted and each sentence carries a distinct fact.

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?

The tool is simple, but with no output schema the description should characterize the report returned on completion; it only covers the in-progress 'running' case and retryAfter. An agent finishing a poll loop has no description of what a completed or failed result looks like.

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 100% and the single jobId parameter is already documented in the schema with the same provenance note, so the description adds no meaning beyond a restatement. The 3 baseline applies where the schema does the heavy lifting.

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 (Fetch) and resource (the report) and scopes it to a jobId produced by verify_b20_token, which cleanly separates it from that sibling's job-starting role.

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?

Gives the clear precondition that a jobId from verify_b20_token is required, plus an explicit polling rule: if status is 'running', wait retryAfter seconds before calling again. It stops short of stating what to do if the job fails or is unknown, and names no alternative tool for that 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.