Skip to main content
Glama

check_charge

Builds the USDC transfer of the Check price for the networks and paid tools chosen (networks from check_info checkNetworks, tools from check_info toolOffer: the sum of each tool at its own price, never above its maximum) from payer to the analysis fee wallet on chainId (any network of check_info networks), for the payer to sign. The credit is bound to those networks. Needs buyProof, the purchase proof of THIS payer from check_buy_proof (the payer signed and passed the free screening); without it, or with another wallet's, check_buy_proof_required (401). The server also measures the sender on-chain. Returns { check { id, status awaiting_payment, amount, amountRaw, token, feeWallet, tools (exactly what this Check reads) }, skippedChecks? (tools asked for that are switched off or not on sale, left out and not charged), transaction, plan (buildId check-, steps on EVM or transaction on Solana), report }. check.id (CHK-...) is the capability of this Check: whoever holds it reports the payment, analyses and reads the result, so keep it private and keep it to come back to the result. Each call makes a NEW Check, good for 30 minutes (expiresAt): a transaction mined after that is credited by the price of now on the networks it covers (check_report_payment). Pass checkId of one still awaiting payment and in its time to rebuild its transfer (the Solana one expires in about a minute). Sign the transaction exactly as returned: it carries the mark of THIS Check (16 bytes after the transfer arguments on EVM, a memo on Solana). A transfer you build yourself is refused with analysis_payment_rejected reason charge_not_tied after the money left: do not pay again, prove the wallet with destination_challenge (receiver = details.feeWallet, chargeId = the check id, chargeTxHash = that hash) and destination_authorize, then report the same hash again. Refusals: analysis_tool_unavailable (503, a tool is down: nothing is built), check_credit_limit (409), payer_blocked (403), check_network_unsupported (400), check_networks_required (400), check_already_paid (409, checkId of a paid Check), check_charge_expired (409), kyc_required (403, tools with crystal and no approved KYC), invalid_check (400, tools empty, repeated or unknown), check_unavailable (503, no tool chosen is on sale).

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": {
      "chainId": "<chainId>",
      "payer": "<payer>",
      "networks": "<networks>",
      "buyProof": "<buyProof>"
    },
    "name": "check_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
payerYesThe paying wallet, the one that signs the transfer (0x on EVM, base58 on Solana).
toolsNoThe paid tools to buy, at least one, each once (owner, 18/11/2026: one mark per paid tool): any of "scorechain" (once per wallet), "merkle-science" and "crystal" (once per network), from check_info toolOffer. The Check reads and shows ONLY these, plus the free OFAC and issuer freeze screening. crystal only for a payer whose identity check (KYC) is approved: otherwise kyc_required (403) and nothing is built. Left out, the pair scorechain and merkle-science (older clients). Here ["crystal"] means Crystal ALONE (CLI 0.3.15 and older, on the /v1, still get the pair plus Crystal for it).
chainIdYesEVM: integer from GET /v1/chains (1, 10, 56, 100, 137, 8453, 42161, 43114, 130). Solana: string from GET /v1/svm/chains ("solana-mainnet").
checkIdNoOptional: a Check still awaiting payment, to rebuild its transfer instead of making a new Check.
buyProofYesThe purchase proof of this payer from check_buy_proof (vcb_..., 10 minutes). Secret.
networksYesThe networks to analyse, from check_info checkNetworks (e.g. ["1","8453","solana-mainnet"]). The price is perNetwork times these, never above maximum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tools / description
      Previous value: -"Optional: [\"crystal\"] adds Crystal on every network chosen, at the optionalTools price of check_info. Only for a payer whose identity check (KYC) is approved: otherwise kyc_required (403) and nothing is built. Scorechain and Merkle Science always run."New value: +"The paid tools to buy, at least one, each once (owner, 18/11/2026: one mark per paid tool): any of \"scorechain\" (once per wallet), \"merkle-science\" and \"crystal\" (once per network), from check_info toolOffer. The Check reads and shows ONLY these, plus the free OFAC and issuer freeze screening. crystal only for a payer whose identity check (KYC) is approved: otherwise kyc_required (403) and nothing is built. Left out, the pair scorechain and merkle-science (older clients). Here [\"crystal\"] means Crystal ALONE (CLI 0.3.15 and older, on the /v1, still get the pair plus Crystal for it)."
    • changedInput schema / properties / tools / items / enum
      Previous value: -[
      -  "crystal"
      -]New value: +[
      +  "scorechain",
      +  "merkle-science",
      +  "crystal"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / tools
      Added value: +{
      +  "description": "Optional: [\"crystal\"] adds Crystal on every network chosen, at the optionalTools price of check_info. Only for a payer whose identity check (KYC) is approved: otherwise kyc_required (403) and nothing is built. Scorechain and Merkle Science always run.",
      +  "items": {
      +    "enum": [
      +      "crystal"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / buyProof
      Added value: +{
      +  "description": "The purchase proof of this payer from check_buy_proof (vcb_..., 10 minutes). Secret.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "chainId",
      -  "payer",
      -  "networks"
      -]New value: +[
      +  "chainId",
      +  "payer",
      +  "networks",
      +  "buyProof"
      +]
  4. Changed5 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"
      -}
    • addedInput schema / properties / checkId
      Added value: +{
      +  "description": "Optional: a Check still awaiting payment, to rebuild its transfer instead of making a new Check.",
      +  "type": "string"
      +}
    • addedInput schema / properties / networks
      Added value: +{
      +  "description": "The networks to analyse, from check_info checkNetworks (e.g. [\"1\",\"8453\",\"solana-mainnet\"]). The price is perNetwork times these, never above maximum.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / payer / description
      Previous value: -"The paying wallet (0x on EVM, base58 on Solana)."New value: +"The paying wallet, the one that signs the transfer (0x on EVM, base58 on Solana)."
    • changedInput schema / required
      Previous value: -[
      -  "chainId",
      -  "payer",
      -  "access"
      -]New value: +[
      +  "chainId",
      +  "payer",
      +  "networks"
      +]
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only supply the generic safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true); the description adds the non-obvious behavior that matters: every call mints a NEW Check with a 30-minute expiry, the transaction carries a per-Check mark and must be signed exactly as returned, the Solana plan expires in about a minute, credit is bound to the chosen networks, and omitted/on-sale-disabled tools are skipped and not charged. It also documents server-side on-chain sender measurement.

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 core action, prerequisites, and return shape are front-loaded, which is good, but the description runs 400+ words of dense run-on clauses and appends a long error catalogue that partially duplicates points already made (expiry, paid Check, self-built transfer). Most sentences earn their place, but the density hurts scannability.

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 high-stakes payment-building tool with no output schema, the description supplies the full return object (check.id/status/amount/feeWallet/tools, skippedChecks, transaction, plan, report), the privacy contract on check.id, and the refusal codes with their meanings. An agent has what it needs to call, sign, and recover from the documented failure modes.

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 100%, so the schema already documents all six parameters; the description still adds real pricing semantics not in the schema ('the sum of each tool at its own price, never above its maximum'), the credit-binding meaning of networks, and the secret/10-minute nature of buyProof. Marginal gain over a 100%-covered schema keeps it below 5.

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?

Opens with a concrete verb+object: 'Builds the USDC transfer of the Check price ... from payer to the analysis fee wallet on chainId ... for the payer to sign.' It names the exact inputs that scope the build (networks from check_info checkNetworks, tools from toolOffer) and implicitly separates itself from check_report_payment and check_buy_proof by describing a distinct step in the flow.

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

Usage Guidelines5/5

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

Explicit prerequisites (buyProof from check_buy_proof proving THIS payer passed screening), explicit re-use path (pass checkId of a Check still awaiting payment to rebuild), and explicit failure alternatives (a self-built transfer triggers charge_not_tied, recover via destination_challenge + destination_authorize). It also states when NOT to pay again: 'do not pay again'.

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