Skip to main content
Glama

BRAINIAC Equity Analytics

Validate ISIN, CUSIP and SEDOL check digits

equity-analytics_security-identifier-validate
Read-onlyIdempotent

Detect identifier type by pattern, validate check digits, and optionally convert CUSIP or SEDOL to ISIN. Existence is not confirmed. Price $0.02 USDC. POST /api/v1/equity-analytics/security-identifier-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "identifiers": "<identifiers>"
    },
    "name": "equity-analytics_security-identifier-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toIsinNotoIsin, object. Optional.
identifiersYesidentifiers, array. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses three material behaviors: existence is not confirmed, the call costs $0.02 USDC, and an unpaid call returns x402 payment terms without executing. The payment-gating failure mode is exactly the kind of context an agent cannot get from annotations. It stops short of describing batch behavior or partial-failure handling for the array input.

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?

Four short sentences, capability stated first, then the critical limitation, then cost and the payment failure mode. No filler and nothing buried at the end.

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?

With annotations covering safety and an output schema covering return values, the description fills the remaining gaps: payment, endpoint, and the existence caveat. The one omission is how the identifiers array behaves on mixed valid/invalid input (per-item results vs. whole-call failure), which matters for a batch tool.

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%, so baseline is 3, but the description earns more by explaining what the optional toIsin object actually does (convert CUSIP or SEDOL into an ISIN), which the schema's generic 'toIsin, object. Optional.' does not convey. The two-character country prefix field remains unexplained, though the conversion sentence makes its purpose inferable.

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

Purpose4/5

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

The description gives specific verbs and resources: 'Detect identifier type by pattern, validate check digits, and optionally convert CUSIP or SEDOL to ISIN.' Naming the covered identifier types (ISIN, CUSIP, SEDOL) implicitly separates it from the sibling lei-validate, though it never states the contrast directly.

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 by the stated scope ('Existence is not confirmed' tells the agent this is a format/check-digit test, not a registry lookup), but there is no explicit when-to-use or when-not-to-use guidance and no mention of when to supply the optional toIsin conversion versus validating alone.

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.

Resources