Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

verify_gblin_authorization

Read-onlyIdempotent

Checks a signed GBLIN authorization on-chain before gas is spent, returning a would-settle verdict with calldata or the failing reason.

Instructions

Checks a signed GBLIN authorization against the chain before any gas is spent on it. Recovers the signer from the EIP-712 digest (and asks the wallet itself through ERC-1271 when the payer is a contract), then checks the validity window against on-chain time, whether the nonce has already been used or cancelled, and whether the payer still holds the amount. Returns a verdict and the ready calldata when it would settle, the failing reason when it would not. These are the checks an x402 facilitator runs, so a 'would_settle' verdict means the payment can be carried.

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": {
      "authorization": "<authorization>",
      "signature": "<signature>"
    },
    "name": "verify_gblin_authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoWhich method the signature was produced for. Default 'receive'.
signatureYesThe signature produced by the payer's wallet, 0x-prefixed.
authorizationYesThe authorization object: from, to, value, validAfter, validBefore, nonce.

Output Schema

NameRequiredDescriptionDefault
amountNo
checksYes
digestNo
methodYes
sourceNo
submitNoCalldata and who may submit it, or null when it would not settle.
failuresYesReasons it would not settle; empty when it would.
would_settleYesTrue only if the token would accept this authorization now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations, which only declare read-only, idempotent, non-destructive, open-world. It enumerates the exact checks (EIP-712 signer recovery, ERC-1271 for contract payers, validity window vs on-chain time, nonce used/cancelled, payer balance) and the two possible outcomes: ready calldata or failing reason. That tells the agent its network-dependency and failure behavior concretely.

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?

Front-loads the purpose and then the checks, with the outcome stated last; every sentence carries information. It is somewhat dense for three sentences, but nothing is redundant with the annotations or the schema.

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?

Complete for a complex, nested-input verification tool. With an output schema present, the description need not detail return values, yet it still signals a verdict plus calldata or a failing reason, and it covers the cross-cutting concerns (contract payers, on-chain time, nonce state) that make the tool's result interpretable.

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 schema documents all three parameters, including the method enum default, so the baseline of 3 applies. The description adds domain meaning (signature is verified by signer recovery, ERC-1271 fallback for contract payers) but does not explain the receive/transfer method distinction or the authorization object fields beyond what the schema says.

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 (checks a signed GBLIN authorization) plus the decisive scope detail: before any gas is spent. This distinguishes it from the sibling prepare_gblin_payment and relay_gblin_payment as a read-only pre-flight check rather than an action that submits.

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 clear situational context ('before any gas is spent on it') and frames the verdict against what an x402 facilitator checks, so the agent knows when to reach for it. It stops short of naming explicit alternatives or exclusions, e.g., when to use prepare_gblin_payment or relay_gblin_payment instead.

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