Skip to main content
Glama

popcorn_time

Destructive

Request signed current-time evidence. Defaults to a free unpaid 402 challenge. A fresh receipt costs exactly $0.001 USDC on Base. Payment requires owner approval, approve_payment:true, and a caller-signed payment_signature. No server wallet or private key. No automatic retry. Verify evidence and account for client round-trip time before a deadline decision.

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

Input Schema

NameRequiredDescriptionDefault
freshness_msNoHow fresh the signed time evidence must be, in milliseconds. Default 30000, allowed from 100 to 60000.
approve_paymentNoSet to true to approve paying exactly $0.001 USDC on Base for this single call. Requires payment_signature.
payment_signatureNoCaller-signed x402 PAYMENT-SIGNATURE. Never send a wallet private key. Requires approve_payment:true for this single call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / approve_payment / description
      Added value: +"Set to true to approve paying exactly $0.001 USDC on Base for this single call. Requires payment_signature."
    • addedInput schema / properties / freshness_ms / description
      Added value: +"How fresh the signed time evidence must be, in milliseconds. Default 30000, allowed from 100 to 60000."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the payment cost and currency/chain, the approval requirement, that no server wallet or private key is held, and that there is no automatic retry — all material for an agent that must not accidentally incur charges. It does not explain the destructiveHint=true annotation (what state is consumed or the consequences of a failed payment), which leaves a gap for a non-idempotent, non-read-only tool.

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, then payment terms, then the operational caveat; every sentence carries information an agent needs before calling. The style is somewhat telegraphic and fragmented, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still covers the payment flow, the free default, the approval gate, and the downstream verification step, which is what an agent needs to invoke it safely. It omits what the returned receipt actually contains and how a 402 challenge is surfaced, which is a modest gap for a paid, non-idempotent tool.

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 already 100%, so the baseline is 3; the description adds real value by stating the coupling between approve_payment:true and a caller-signed payment_signature, and by affirming that no private key is ever supplied. The freshness_ms window is not discussed in prose, but the schema documents it fully, so nothing is lost.

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 and resource ('Request signed current-time evidence') and makes the payment-versus-free distinction explicit, so an agent knows this tool obtains time attestations rather than verifying them (it names verification as a follow-up step). It does not differentiate against the other siblings (catalog, hash, sample, witness), which keeps it short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent the default path (free unpaid 402 challenge) and the condition that switches to the paid path (a fresh receipt at exactly $0.001 USDC), plus the explicit precondition of owner approval. It also gives a decision-relevant caveat about round-trip latency before deadlines. No sibling-level routing guidance is given beyond 'verify evidence', so no exclusion of alternatives.

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.