Skip to main content
Glama

Agent Bits

by io.github.rwaldman

isbn_validate

Verify whether an ISBN-10 or ISBN-13 passes checksum rules and return normalized digits when checking book identifiers before catalog or purchase flows.

Use when:

  • Is this ISBN valid?

  • Check the checksum for an ISBN-13 book identifier

  • Normalize and validate an ISBN-10 or ISBN-13 string

Do not use when:

  • Look up book title, author, or cover metadata from an ISBN

  • Validate UUIDs (use uuid_validate) or payment-card Luhn numbers (use luhn_validate)

  • Validate arbitrary barcode formats that are not ISBN-10/13

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesISBN-10 or ISBN-13 candidate

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the core behavior (validation and normalization), but lacks details on return format, error handling, or what 'normalized' means exactly. For a validator, this is adequate but not thorough.

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

Conciseness5/5

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

The description is concise, front-loaded with the purpose, and structured with clear bullet lists. Every sentence adds value; no redundant or filler content.

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?

The tool is simple (1 param, no output schema), but since there is no output schema, the description should specify the return shape. It says 'return normalized digits' but not the full return structure (e.g., boolean plus normalized value). This is a meaningful gap, though the usage sections are comprehensive.

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 the single parameter 'value' is described as 'ISBN-10 or ISBN-13 candidate'. The description reinforces the accepted formats but does not add substantial new meaning beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

The description states a specific verb+resource: 'Verify whether an ISBN-10 or ISBN-13 passes checksum rules and return normalized digits'. It clearly distinguishes from sibling validation tools (uuid_validate, luhn_validate) by focusing on ISBN formats and explicitly naming alternatives in the 'Do not use' section.

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

Usage Guidelines5/5

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

The description includes explicit 'Use when' and 'Do not use when' sections with concrete examples, and names alternative tools (uuid_validate, luhn_validate) for other validation tasks. This gives clear decision criteria.

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

All Agent Bits toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear use cases and explicit 'Do not use when' guidance preventing confusion. For example, base64_decode and url_decode handle different encoding schemes, while timestamp_convert and timezone_convert address separate time operations.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., base64_decode, country_lookup, uuid_validate). While verbs vary (decode, encode, lookup, validate, convert), the naming format is uniform and predictable.

Tool Count4/5

The 18-tool set is slightly above the typical 3-15 range, but the breadth is justified by the server's purpose as a general-purpose utility toolkit. Each tool earns its place, and the count does not feel overwhelming or redundant.

Completeness4/5

The toolkit covers encoding/decoding, validation, lookups, and conversions across common developer needs. Minor gaps exist, such as no UUID generation tool to complement uuid_validate, and no HTML entity encoding/decoding, but these are not critical omissions for the stated utility scope.

Resources