Skip to main content
Glama

Verify a CAS registry number

bpj_cas_registry_check
Read-onlyIdempotent

Check the weighted final digit of a hyphenated CAS Registry Number.

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": {
      "value": "<value>"
    },
    "name": "bpj_cas_registry_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive check. The description adds that only the weighted final digit is verified and that the input must be hyphenated, but it does not state what a failed check returns or how malformed input is handled.

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 a single, front-loaded sentence with no unnecessary wording. Every word contributes to identifying the operation and the expected input.

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?

For a simple one-parameter validator, the description covers purpose and input shape. However, with no output schema, it leaves the return value and failure behavior unstated, so an agent cannot fully predict the result of calling it.

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?

The sole parameter 'value' has 0% schema description coverage, so the description must compensate. It identifies the input as a hyphenated CAS Registry Number, which is useful, but it provides no format pattern, example, or other validation details.

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 ('Check') and a precise resource ('weighted final digit of a hyphenated CAS Registry Number'). This clearly distinguishes it from sibling check-digit tools such as CUSIP, ISSN, or IMEI validators.

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

Usage Guidelines3/5

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

Usage is implied: the tool is for verifying a CAS Registry Number. The description does not explicitly say when to use this versus alternatives or when not to use it, so guidance is adequate but minimal.

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.