Skip to main content
Glama

sootool.verify_receipt

Read-onlyIdempotent

Re-executes a calculation from tool and arguments to verify receipt integrity by comparing input, result, version, and policy hashes; optionally checks signatures and returns valid/mismatches.

Instructions

계산 영수증(_meta.integrity)을 재실행으로 검증한다. tool 과 arguments 로 같은 계산을 다시 실행해 입력 해시, 결과 해시, 도구 버전, 정책 해시를 대조하고, 서명이 있으면 public_key_b64 로 서명을 검증한다. valid 와 mismatches 를 반환한다. core.batch, core.pipeline 도 재실행 검증 대상이지만, 저장된 스냅샷에서 이어 실행하는 core.pipeline_resume 은 재현되지 않아 대상이 아니다.

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": {
      "tool": "<tool>",
      "arguments": "<arguments>",
      "receipt": "<receipt>"
    },
    "name": "sootool.verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
receiptYes
argumentsYes
public_key_b64No
require_signatureNo

Output Schema

NameRequiredDescriptionDefault
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
validYes
warningsYes
mismatchesYes
recomputedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the important traits: the tool itself re-executes another tool with the supplied arguments, verifies an optional signature when public_key_b64 is given, and reports valid/mismatches. It also flags the reproducibility boundary for pipeline_resume, which annotations cannot express.

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?

Four front-loaded sentences with no filler: purpose/mechanism, verification checks, return values, then target exclusions. The hash enumeration is slightly dense but each clause carries information.

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?

Given 5 parameters at 0% schema coverage, a nested receipt object, and an output schema, the description covers mechanism, all meaningful inputs, the return fields, and the reproducibility exclusions. Nothing essential to deciding or invoking it 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 description coverage is 0%, so the description must carry parameter meaning, and it does: tool+arguments are the re-execution inputs, receipt is the _meta.integrity payload, public_key_b64 enables signature verification. require_signature is only implicitly covered via '서명이 있으면', which is a minor gap.

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?

It names a specific verb (검증한다) and resource (계산 영수증/_meta.integrity), and it explains the mechanism — re-running the computation and cross-checking input hash, result hash, tool version, and policy hash. No sibling tool does receipt verification, so the purpose stands out clearly against the list of calculators.

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?

It explicitly names which tools are valid targets (core.batch, core.pipeline) and which is not (core.pipeline_resume, because its snapshot-based continuation is not reproducible). That is exactly the when/when-not routing an agent needs before calling it.

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

Deploy Server

Other Tools