Skip to main content
Glama

check_result

Read-onlyIdempotent

Reads one Check by its id, as stored (status, target, seal, result, screening, networks, events). Never calls a paid provider. An unknown id gets check_not_found (404).

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": {
      "checkId": "<checkId>"
    },
    "name": "check_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkIdYesThe Check id from check_charge (CHK-...). It is the capability of this Check: keep it, and keep it private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / access
      Removed value: -{
      -  "description": "The Check access of this payer from check_access (vca_...). Secret: it reads and spends this payer's credits.",
      -  "type": "string"
      -}
    • changedInput schema / properties / checkId / description
      Previous value: -"The check id (CHK-...)."New value: +"The Check id from check_charge (CHK-...). It is the capability of this Check: keep it, and keep it private."
    • removedInput schema / properties / payer
      Removed value: -{
      -  "description": "The wallet that paid.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "checkId",
      -  "payer",
      -  "access"
      -]New value: +[
      +  "checkId"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description still adds genuine context beyond them: no paid provider call is made, the returned field set is named, and the 404 / check_not_found outcome for an unknown id is disclosed.

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: action and return fields first, then the cost guarantee, then the failure mode. Nothing is redundant and every clause carries information.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description supplies the returned field list, the no-cost guarantee, and the error outcome. An agent has everything needed to call it correctly and interpret an unknown-id response.

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 description coverage is 100% and the checkId property already documents the CHK- prefix and its capability/privacy semantics. The description only says 'by its id', adding no format or sourcing detail beyond the schema, so the baseline 3 applies.

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 ('Reads one Check by its id, as stored') and enumerates the payload ('status, target, seal, result, screening, networks, events'). The clause 'Never calls a paid provider' plus 'as stored' separates it from the charge/analyze siblings that presumably create or compute a Check.

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: an agent can infer this is the free way to re-read an existing Check, and that an unknown id yields check_not_found (404). There is no explicit 'use this instead of X when...' routing to siblings such as check_charge or check_analyze.

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