Skip to main content
Glama
starshield-forensics

starshield-forensics

by Ziqi

Validate Payment & Banking Checksums Offline

starshield_validate_financial_iocs
Read-onlyIdempotent

Validates financial indicators of compromise by extracting and checksum-verifying card numbers, IBANs, SWIFT/BIC codes, and UK sort-code/account pairs from text offline.

Instructions

Scan text offline in <1ms to extract and mathematically verify ISO/IEC 7812 Luhn card numbers, 89-country ISO 13616 IBAN Mod-97 accounts, 250-territory ISO 9362 SWIFT/BIC codes, and intra-message UK Faster Payments Sort Code + 8-digit Account pairs.

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": {
      "text": "<text>"
    },
    "name": "starshield_validate_financial_iocs"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText snippet, invoice instruction, or chat note to validate offline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the operation is entirely offline, sub-millisecond, and validation is mathematical (checksum) rather than heuristic, plus the important constraint that Sort Code + Account pairs are only matched intra-message. It stops short of saying what the response contains, but the added traits are substantive.

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

Conciseness4/5

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

A single sentence with the performance and offline claims front-loaded, followed by the enumerated validator families. The dense standards-and-country-count phrasing is information-bearing rather than filler, though the four-part enumeration makes it heavier to parse than necessary; minor trimming would improve it.

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 one-parameter, no-output-schema tool, the description covers what is scanned and which standards are validated, and the intra-message pairing note heads off a likely false assumption. It does not indicate the shape of the result (e.g., matched spans, type labels, pass/fail per candidate) or how non-matching text is handled, which matters because no output schema exists to fill that gap.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that 'text' is the snippet to validate offline. The description reinforces the input domain implicitly through the listed identifier standards but adds no syntax, length, or formatting guidance beyond what the schema states. Baseline 3 applies when the schema carries the parameter documentation.

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 uses a concrete verb pair ('extract and mathematically verify') applied to four precisely enumerated resources, each tied to a named standard (ISO/IEC 7812 Luhn, ISO 13616 IBAN Mod-97, ISO 9362 SWIFT/BIC, UK Faster Payments). An agent knows exactly what class of entities this tool finds and validates, and the sibling tools (demo, image tamper inspection, LevelDB precheck) share no scope with it.

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 'Scan text offline' and the examples of input sources in the schema, so an agent can infer this is the tool for checking payment identifiers in free text. However, there is no explicit when-to-use statement, no when-not-to-use condition, and no routing to an alternative tool for related tasks such as non-financial IOC extraction.

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