Skip to main content
Glama

grid402_verify

Read-onlyIdempotent

Stateless verification of an _oracle_proof ECDSA secp256k1 signature (free).

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": {
      "payload": "<payload>"
    },
    "name": "grid402_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesFull JSON response object containing the _oracle_proof block to verify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payload / description
      Previous value: -"JSON object with the _oracle_proof block to verify"New value: +"Full JSON response object containing the _oracle_proof block to verify."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds two genuine behavioral facts beyond that: verification is stateless (no server-side session or stored artifact) and free (no billing). It stops short of describing outcome behavior on an invalid or malformed proof.

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?

One sentence, front-loaded with the verb and resource, with the two most decision-relevant qualifiers (stateless, free) in immediate proximity. No filler and nothing repeated from the name.

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 (one nested parameter object), and annotations carry the safety semantics, but there is no output schema and the description never says what a verification returns—a boolean, an error, decoded claim details—or how failure is surfaced. For a verification tool whose entire purpose is producing a verdict, that is a meaningful gap.

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?

With a single parameter at 100% schema coverage, the schema already explains that payload is the full JSON response object containing the _oracle_proof block. The description adds nothing about the parameter shape, size, or what happens if that block is absent, so the baseline 3 applies.

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?

Names a specific verb (verify) and a specific resource (_oracle_proof ECDSA secp256k1 signature), plus the qualifier 'stateless' that scopes the operation. An agent can distinguish it from nearby tools like grid402_crypto or grid402_notarize by the proof-verification framing, though the description never names an alternative explicitly.

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: verifying a proof you already hold, with 'stateless' signaling no prior setup and '(free)' signaling no cost. There is no explicit when-to-use/when-not-to-use guidance and no routing to a sibling tool if the caller instead needs to create or fetch a proof.

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