Skip to main content
Glama

popcorn_hash

Read-onlyIdempotent

Hash public bytes on this remote server. Submitted text reaches the server: hash private work locally instead. Free; no onward request or payment.

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_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
payload_textNoThe public text to hash on this server. Submitted text reaches the server, so hash private work locally instead. Give one of payload_text or payload_base64url.
payload_base64urlNoThe public bytes to hash, given as base64url. Submitted bytes reach the server, so hash private work locally instead. Give one of payload_text or payload_base64url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payload_base64url / description
      Added value: +"The public bytes to hash, given as base64url. Submitted bytes reach the server, so hash private work locally instead. Give one of payload_text or payload_base64url."
    • addedInput schema / properties / payload_text / description
      Added value: +"The public text to hash on this server. Submitted text reaches the server, so hash private work locally instead. Give one of payload_text or payload_base64url."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them: it discloses that payloads are transmitted to and visible on the remote server, and that there is no cost or onward request. It stops short of saying what the hash function or output encoding is.

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?

Three short sentences, front-loaded with the action, then the risk, then the cost posture. Nothing is padded, though the privacy warning is already duplicated inside both parameter descriptions, so a small redundancy exists across the definition.

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 only two mutually exclusive string parameters and rich annotations, most of what an agent needs is present. However, there is no output schema and the description never says what comes back — which algorithm, what encoding (hex/base64), whether a salt or server-attestation is included. For a hashing tool that is a notable gap for correct downstream use.

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% and both parameters are fully documented inline, including the either/or constraint between payload_text and payload_base64url. The description itself adds no parameter meaning beyond the schema; it only restates the privacy warning the schema already carries. Baseline 3 applies.

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 first sentence supplies a concrete verb and resource ('Hash public bytes') plus deployment context ('on this remote server'), which distinguishes it from a local-hash utility. It does not explicitly contrast with any sibling, but the siblings (catalog, sample, time, verify, witness) are different operations, so the risk of confusion is low.

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?

The description gives a clear when-not condition: hash private work locally instead, because submitted text reaches the server. It also establishes the cost/network posture ('Free; no onward request or payment'), which is decision-relevant. What it lacks is an explicit positive trigger sentence (e.g. 'use when you want a server-attested hash of public data').

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.