Skip to main content
Glama

popcorn_verify

Read-onlyIdempotent

Verify a time or witness receipt using caller-trusted JWKS and expected values. Digest-only for witness payloads. No outbound request or payment. Caller keys do not establish issuer identity; a signature grants no authority.

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": {
      "receipt_type": "<receipt_type>",
      "response": "<response>",
      "jwks": "<jwks>",
      "verification": "<verification>"
    },
    "name": "popcorn_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
jwksYesThe JWKS you trust, holding the keys the receipt signature is checked against.
responseYesThe receipt response to verify, as returned by the time or witness call.
receipt_typeYesThe kind of receipt being verified: time or witness.
verificationYesThe expected values the receipt is checked against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / jwks / description
      Added value: +"The JWKS you trust, holding the keys the receipt signature is checked against."
    • addedInput schema / properties / receipt_type / description
      Added value: +"The kind of receipt being verified: time or witness."
    • addedInput schema / properties / response / description
      Added value: +"The receipt response to verify, as returned by the time or witness call."
    • addedInput schema / properties / verification / description
      Added value: +"The expected values the receipt is checked against."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, closed-world, non-destructive), the description adds real behavioral context: no outbound request or payment is made, witness payloads are handled digest-only, and the trust model is explicitly bounded ('caller keys do not establish issuer identity; a signature grants no authority'). That security caveat is the kind of context structured fields cannot convey. What it omits is failure/return behavior, e.g. what a failed verification looks like.

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 short sentences, front-loaded with the action and followed by scope limits and trust caveats in descending order of importance. No filler, though the density of security caveats makes it slightly terse for a first-time caller.

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?

With no output schema and four required parameters including nested objects, the description should say what a successful or failed verification yields (boolean, error, mismatch details). It covers inputs and trust constraints well but leaves the return contract entirely unspecified.

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 coverage is 100%, so all four parameters already carry descriptions and the baseline is 3. The description echoes the jwks and verification semantics and adds one genuinely new constraint, 'digest-only for witness payloads', which informs the witness enum branch, but it does not explain the shape of the 'verification' expected-values object.

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?

The description opens with a specific verb+resource pair ('Verify a time or witness receipt') and names the mechanism (caller-trusted JWKS plus expected values), so an agent knows exactly what operation this is. It does not differentiate itself from the sibling popcorn_verify_v2, which is the only thing keeping it from a 5.

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: an agent can infer this is the verification step after popcorn_time or popcorn_witness returns a receipt. There is no explicit when-to-use versus when-not, and no guidance on choosing this over popcorn_verify_v2 despite that sibling existing.

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.