Skip to main content
Glama

SHA3-512 hex length, input discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

sha3-512

SHA3-512 hex length, input discarded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects and output behavior, but it only says input is discarded and references a hex length. It does not state the return value, whether hashing actually occurs, or whether the URL/website/JSON parameters are truly ignored despite their schema descriptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only five words, so it is concise and front-loads the algorithm, but it is telegraphic: it is a fragment rather than a sentence and omits the verb that would make the purpose unambiguous.

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

Completeness2/5

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

For a tool with 10 optional parameters, no output schema, and no annotations, this one-line fragment is insufficient. It leaves the return format, constant-vs-computed behavior, and side-effect profile unspecified, so an agent cannot invoke it with confidence.

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% and all 10 parameters are optional, so the baseline is 3. The phrase 'input discarded' does add a global semantic—arguments are irrelevant—but it conflicts with several parameter descriptions (e.g., url 'normalize or cite', website 'to check for agent readiness') and doesn't clarify per-parameter behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase—'SHA3-512 hex length, input discarded'—with no verb stating what the tool computes or returns. It adds 'hex length' and 'input discarded' to the tool name, but an agent cannot tell whether it returns a hash digest, a fixed length, or simply ignores all parameters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No statement about when to call this tool or when to prefer a sibling. 'input discarded' hints that arguments are irrelevant, but it never says 'use when you need the SHA3-512 hex length' or names any alternative.

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

All SHA3-512 hex length, input discarded toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources