Skip to main content
Glama

check_info

Read-onlyIdempotent

The paid Check of any wallet (owner, 18/11/2026: one mark per paid tool, the person chooses which; the free OFAC and issuer freeze screening always runs). toolOffer [{ tool, per ("wallet" or "network"), price, maximum, kycRequired? }]: each paid tool on sale, at its own price (dollars as text): scorechain per wallet (one reading answers every network of the family: an EVM wallet and a Solana one are two), merkle-science and crystal per network, each never above its maximum; crystal only for a payer with an approved KYC. A tool switched off or without a price is not listed. The price of a Check is the SUM over the tools chosen of price x units (wallets or networks), each capped at its maximum: the same reckoning check_charge charges. tools: the names on sale; defaultTools: what check_charge buys without tools (the pair, for older clients); freeScreening: ["ofac", "issuer-freeze"]. price { perNetwork, maximum, amount, currency }: Merkle Science alone, for older clients. checkNetworks [{ chainId, family }] (the seven to choose: 1, 10, 56, 137, 8453, 42161, solana-mainnet), networks [{ chainId, family, token (the USDC that pays), feeWallet }] (where it is paid: the nine EVM networks and solana-mainnet), creditLimit and chargeValidSeconds (1800). Public, no proof needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower, and the description still adds real context beyond them: the endpoint is public with no proof required, there is a creditLimit, and quotes are valid for chargeValidSeconds (1800). The pricing formula (sum of price x units, each capped at maximum) is disclosed so the agent can predict what a subsequent charge will cost; what is missing is whether prices or the network set change over time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is mostly load-bearing because it substitutes for a missing output schema, but the delivery is a single dense paragraph of nested parentheticals with no field list formatting, and the pricing-formula sentence is hard to parse. Backwards-compatibility asides ('for older clients' on both price and defaultTools) consume space that could have gone to a crisper statement of purpose up front.

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 zero-parameter, read-only configuration tool with no output schema, the description covers nearly everything an agent needs: the fee model, per-tool and per-network billing units, the KYC constraint on crystal, the seven selectable chains, the nine-plus-Solana fee-wallet networks, and quote validity. What remains thin is the exact shape of the returned JSON and whether the enumerated network list is stable.

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?

With zero input parameters the baseline is 4, and the description instead spends its effort mapping the fields the caller will receive (toolOffer, tools, defaultTools, freeScreening, checkNetworks, networks, creditLimit), which is genuinely additive given there is no output schema. No additional input semantics are possible here.

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 opening sentence establishes that this returns the pricing and configuration for a paid Check, and later clauses ('the same reckoning check_charge charges', 'what check_charge buys without tools') make clear this tool quotes while check_charge buys, which differentiates it from a close sibling. The phrasing is cluttered and never states the purpose in one clean verb+resource sentence, so an agent must assemble the intent from fragments.

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: the repeated references to check_charge and the 'Public, no proof needed' note suggest this is the pre-flight quote an agent reads before charging, and the note that a switched-off tool or one without a price is not listed implies exclusions. However, there is no explicit 'call this before calling check_charge' instruction and no guidance on when to prefer this over check_credits or the quote-style siblings.

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