Skip to main content
Glama

Verify storage temperatures on chain

verify_temp
Read-onlyIdempotent

Verify GYOTAK cold-chain storage temperatures DIRECTLY from the Midnight blockchain. Reads on-chain state and returns decoded hourly temperature records per freezer for independent verification. Unlike the dashboard (which reads from GYOTAK's D1 database), this lets you verify without trusting GYOTAK. Each value is the HOURLY AVERAGE committed on-chain; it does not prove the temperature stayed within any limit at every moment in that hour. Supports both preprod and mainnet.

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": "verify_temp"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoMidnight network (default: mainnet)
freezerIdNoFilter to a specific freezer by ID. Omit to return all freezers.
hourStartUtcNoFilter to a specific hour (e.g. "2026-07-09 11:00:00"). Omit to return all hours.
contractAddressNoMidnight temp-log contract address (64-char hex). Default: mainnet production contract.

Output Schema

NameRequiredDescriptionDefault
errorNoSame text as content when the input or the lookup failed
sourceNoWhere the on-chain state was read from
messageNoSame text as content when there is nothing to show
freezersNo
total_recordsNo
verification_noteNo
availableFreezerIdsNoListed when the filter matched nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "availableFreezerIds": {
      +      "description": "Listed when the filter matched nothing",
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    "error": {
      +      "description": "Same text as content when the input or the lookup failed",
      +      "type": "string"
      +    },
      +    "freezers": {
      +      "items": {
      +        "properties": {
      +          "freezerId": {
      +            "type": "integer"
      +          },
      +          "records": {
      +            "items": {
      +              "properties": {
      +                "avgTempC": {
      +                  "type": "number"
      +                },
      +                "hourStartUtc": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "hourStartUtc",
      +                "avgTempC"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "freezerId",
      +          "records"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "description": "Same text as content when there is nothing to show",
      +      "type": "string"
      +    },
      +    "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"
      +    },
      +    "total_records": {
      +      "type": "integer"
      +    },
      +    "verification_note": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the read-only, idempotent, non-destructive, open-world profile, so the description is free to add the context that matters: it returns decoded hourly temperature records per freezer, it discloses the important limitation that each value is an hourly average and does not prove limits were met at every instant, and it notes preprod/mainnet support. That limitation is material behavioral information an agent could not infer from structured fields.

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?

Purpose and trust-model differentiator are front-loaded in the first two sentences, followed by the output semantics and the averaging caveat. Every sentence carries non-redundant information; nothing is padding.

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 no explanation, and the description still supplies the trust model, the data granularity caveat, and network scope for a zero-required-parameter read tool. Nothing an agent needs to call it correctly is missing.

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%, so the schema already explains network, freezerId, hourStartUtc, and contractAddress. The description adds only a light gloss ('returns decoded hourly temperature records per freezer' and 'Supports both preprod and mainnet'), so baseline 3 is appropriate.

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, resource, and data source: verify temperatures read 'DIRECTLY from the Midnight blockchain.' The contrast with 'the dashboard (which reads from GYOTAK's D1 database)' pins down exactly what this tool is and is not, which is the key distinction among the verify_* siblings.

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 a clear when-to-use rationale — use this when you need verification without trusting GYOTAK — and names the alternative (the dashboard/D1 path) explicitly. It does not explain when to choose this over sibling verify_* tools such as verify_catch or verify_komon, so it stops short of full routing guidance.

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