Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

ISBN check, validate an ISBN: check whether an ISBN-10 or ISBN-13 book number is valid

validate_isbn
Read-only

Check an ISBN-10 or ISBN-13 check digit and convert valid ISBN-10s to ISBN-13. Hyphens and spaces are ignored. Use before cataloguing or ordering books. Example: isbn=0-306-40615-2. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "isbn": "<isbn>"
    },
    "name": "validate_isbn"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnYesThe ISBN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, but the description adds real behavior the annotations do not: hyphens and spaces are tolerated, ISBN-10s are converted to ISBN-13, failed calls are free while successful ones are billed, and repeats are charged again (consistent with idempotentHint=false). The billing detail is genuinely useful for an agent deciding whether to retry, though the cost sentence is repeated rather than consolidated.

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 core capability, normalization rule, and use case are front-loaded and tight. However, the pricing clause is verbose and redundant ('Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free' followed by 'each call is charged, so repeats are not free'), bloating a simple one-parameter validator.

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?

For a single-parameter read-only tool with no output schema, the description covers input normalization, both accepted formats, the conversion side effect, and the charging model. It doesn't state what a result looks like (valid flag vs. converted ISBN) or how invalid input is reported, which is the main remaining gap.

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 100% but the schema only says 'The ISBN', so the description adds meaningful normalization semantics ('Hyphens and spaces are ignored') plus a concrete example value. That is real value beyond the input schema, though format-preference guidance for ISBN-13 input is not addressed.

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?

States a specific verb and resource ('Check an ISBN-10 or ISBN-13 check digit') and adds a second concrete behavior (convert valid ISBN-10s to ISBN-13). An agent can distinguish this from siblings like validate_luhn, validate_iban, or bic_validate without opening any schema.

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?

'Use before cataloguing or ordering books' gives a clear usage context and implies the buy-side workflow. It does not name an alternative tool or state when not to use it, so it falls short of a 5.

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.