Skip to main content
Glama

Verify catch record on chain

verify_catch
Read-onlyIdempotent

Verify a GYOTAK catch record DIRECTLY from the Midnight blockchain. Reads on-chain state and returns the raw hex plus decoded fields for independent verification. Unlike get_catch_reports (GYOTAK's own list of records: date, district and verify links, never GPS), this lets you verify without trusting GYOTAK. The exact position is not on the chain (only a commitment to it). The region name is a label set by GYOTAK. GYOTAK checks the region range when recording, but the range used is not part of the record, so a third party cannot confirm it from the chain. Supports both preprod and mainnet. batchId also accepts several IDs separated by commas: they are all checked against a single fetch of the contract state, and the response lists found/not-found per ID.

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": {
      "contractAddress": "<contractAddress>"
    },
    "name": "verify_catch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchIdNoFilter to a specific catch record by batchId (e.g. "CR-20261021-37b2b7be"). Omit to return all records in the contract.
networkNoMidnight network (default: mainnet)
contractAddressYesMidnight contract address (64-char hex). Example: bc33d8c05852decd4ef183201a8a9f3c25eabaa46a81786f306b95397ed118ab

Output Schema

NameRequiredDescriptionDefault
errorNoSame text as content when the input or the lookup failed
foundNo
sourceNoWhere the on-chain state was read from
messageNoSame text as content when there is nothing to show
recordsNoAll catch records (no batchId given)
resultsNoSeveral batch IDs
raw_stateNo
match_typeNo
occurrencesNo
verify_urlsNo
match_offsetsNo
batchId_queriedNo
gps_recoverableNo
customer_summaryNo
raw_state_sha256No
tentative_recordsNo
verification_noteNo
presentation_guidanceNo
raw_state_length_bytesNo
tentative_records_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / batchId / description
      Previous value: -"Filter to a specific catch record by batchId (e.g. \"CR-TESTV3-INSIDE-02\"). Omit to return all records in the contract."New value: +"Filter to a specific catch record by batchId (e.g. \"CR-20261021-37b2b7be\"). Omit to return all records in the contract."
    • changedInput schema / properties / contractAddress / description
      Previous value: -"Midnight contract address (64-char hex). Example: 2e519c349331a6aaee82a7ed31aa5e39d6a3995f6cf85ec2256c97cda9a8c302"New value: +"Midnight contract address (64-char hex). Example: bc33d8c05852decd4ef183201a8a9f3c25eabaa46a81786f306b95397ed118ab"
    • changedInput schema / properties / network / description
      Previous value: -"Midnight network (default: preprod)"New value: +"Midnight network (default: mainnet)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "batchId_queried": {
      +      "type": "string"
      +    },
      +    "customer_summary": {
      +      "type": "string"
      +    },
      +    "error": {
      +      "description": "Same text as content when the input or the lookup failed",
      +      "type": "string"
      +    },
      +    "found": {
      +      "type": "boolean"
      +    },
      +    "gps_recoverable": {
      +      "type": "boolean"
      +    },
      +    "match_offsets": {
      +      "items": {
      +        "properties": {
      +          "offset": {
      +            "type": "integer"
      +          },
      +          "window_hex": {
      +            "type": "string"
      +          },
      +          "window_start": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "match_type": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "Same text as content when there is nothing to show",
      +      "type": "string"
      +    },
      +    "occurrences": {
      +      "type": "integer"
      +    },
      +    "presentation_guidance": {
      +      "type": "string"
      +    },
      +    "raw_state": {
      +      "type": "string"
      +    },
      +    "raw_state_length_bytes": {
      +      "type": "integer"
      +    },
      +    "raw_state_sha256": {
      +      "type": "string"
      +    },
      +    "records": {
      +      "description": "All catch records (no batchId given)",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "results": {
      +      "description": "Several batch IDs",
      +      "items": {
      +        "properties": {
      +          "batch_id": {
      +            "type": "string"
      +          },
      +          "decoded": {
      +            "type": "object"
      +          },
      +          "found": {
      +            "type": "boolean"
      +          },
      +          "offsets": {
      +            "items": {
      +              "type": "integer"
      +            },
      +            "type": "array"
      +          },
      +          "window_hex": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "batch_id",
      +          "found"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "description": "Where the on-chain state was read from",
      +      "properties": {
      +        "block_height": {
      +          "type": "integer"
      +        },
      +        "contract_address": {
      +          "type": "string"
      +        },
      +        "indexer_url": {
      +          "type": "string"
      +        },
      +        "network": {
      +          "type": "string"
      +        },
      +        "tx_hash": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "indexer_url",
      +        "contract_address",
      +        "network"
      +      ],
      +      "type": "object"
      +    },
      +    "tentative_records": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "tentative_records_note": {
      +      "type": "string"
      +    },
      +    "verification_note": {
      +      "type": "string"
      +    },
      +    "verify_urls": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / batchId / description
      Previous value: -"Filter to a specific catch record by batchId (e.g. \"SCR-TESTV3-INSIDE-02\"). Omit to return all records in the contract."New value: +"Filter to a specific catch record by batchId (e.g. \"CR-TESTV3-INSIDE-02\"). Omit to return all records in the contract."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantial context beyond them: the position is only a commitment on-chain, the region name is a GYOTAK-set label, the range is not part of the record, and both preprod and mainnet are supported. These are exactly the trust caveats an agent needs before reporting results.

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-loaded with the core action and the sibling contrast, and every caveat sentence carries operational weight. It is dense, with the batchId comma behavior tucked at the end, but no sentence is filler.

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?

An output schema exists, so return values need not be explained, and the description covers the remaining gaps: trust model, network support, multi-ID batching, and the limits of what the chain can prove. Nothing an agent needs to call this correctly is missing.

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 baseline is 3, but the description adds real meaning beyond the schema by explaining that batchId accepts several comma-separated IDs checked against a single contract-state fetch with per-ID found/not-found results. That behavior is not conveyed by the schema.

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 ('Verify a GYOTAK catch record DIRECTLY from the Midnight blockchain') and explicitly distinguishes itself from the sibling get_catch_reports by naming it and its limitations. An agent can tell verify_catch apart from verify_komon/verify_purchase without opening any schema.

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?

Names the alternative (get_catch_reports) and the exact condition that selects this tool: verifying without trusting GYOTAK. It also spells out what cannot be verified from chain (exact position, region range), which tells the agent when this tool will not satisfy a request.

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