USE THIS to verify an ISSN (serial/journal identifier) before relying on it. Checks the mod-11 check digit (which may be 'X') and returns the expected digit when it fails.
| Name | Required | Description | Default |
|---|---|---|---|
| issn | Yes | The ISSN (8 chars; hyphen ignored). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true; the description adds that the check digit may be 'X' and that the tool returns the expected digit on failure, providing useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with a clear imperative, and contains no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains the check digit behavior but omits what the tool returns upon successful validation. For a simple tool with no output schema, this is a notable gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage for the single parameter is 100%, and the schema already describes '8 chars; hyphen ignored'. The description adds no additional parameter meaning, meeting the baseline but not exceeding it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool verifies an ISSN by checking its mod-11 check digit, distinguishing it from sibling validators for other identifiers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises using the tool before relying on an ISSN, but does not specify when not to use it or provide alternatives among the many sibling validators, leaving usage guidance incomplete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a specific identifier or operation (e.g., validate_iban, parse_date, is_holiday). Even similar tools like validate_isbn and validate_isbn10 are distinct by version. There is no overlap or ambiguity.
Most tools follow a verb_noun pattern (validate_xxx, parse_xxx, format_currency). The exception is 'next_holiday', which uses an adjective instead of a verb. Otherwise consistent.
With 47 tools, the set is very large. While each tool is distinct, the count exceeds the recommended range (25+ is considered too many) and may overwhelm users or agents.
Covers a wide array of international identifiers and utilities, but notable gaps exist (e.g., no Canada SIN, India PAN, Mexico CURP). The set is broad but not exhaustive for the domain of data validation.