Skip to main content
Glama

ISBN-13 digit shape, value discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

isbn13-ok

ISBN-13 digit shape, value 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/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'value discarded,' which hints that the tool does not return the input value, but it does not explain what is returned, whether it performs network access, whether it validates checksums, or what side effects exist. The phrase 'digit shape' suggests a format check, but the behavior is largely opaque.

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 extremely short, which is concise, but it is under-specified rather than efficiently informative. The phrase 'value discarded' is the only behavioral detail, and it is ambiguous. A concise description can still be complete; this one is not.

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

Completeness1/5

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

The tool has 10 parameters, no output schema, no annotations, and a two-phrase description. An agent cannot determine which parameter to use, what the tool returns, or what 'ISBN-13 digit shape' means operationally. This is completely inadequate for a tool with this many parameters and no structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema documents all 10 parameters, but the description adds almost no meaning. It does not indicate which parameter is the ISBN-13 input or how the other nine parameters relate to the tool. The description's 'value discarded' could apply to any parameter, but the tool name suggests ISBN-13, and none of the parameters are named 'isbn' or 'isbn13'. This is a significant semantic gap.

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 'ISBN-13 digit shape, value discarded' is terse and cryptic. It names a resource (ISBN-13) and a verb-ish notion ('digit shape'), but it does not state what the tool actually does—whether it validates, extracts, or transforms an ISBN-13, or how the input is supplied. It also does not distinguish itself from siblings like 'jira-key-shape' or 'domain-shape' beyond the ISBN-13 resource.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention that it is a shape-checker for ISBN-13 strings, nor does it explain when an agent should prefer it over other shape/validation tools. The only implied usage is that it relates to ISBN-13 digit shape, which is insufficient.

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

All ISBN-13 digit shape, value 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