Skip to main content
Glama

Japan Business ID

Find business IDs in a document

extract_business_ids
Read-onlyIdempotent

Find and validate invoice registration numbers and corporate numbers inside invoice, receipt or contract text (up to 20,000 characters).

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": "extract_business_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesDocument text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered without prose. The description adds the useful detail that results are validated and the input is capped at 20,000 characters, but says nothing about what happens on no-match, how multiple hits are ordered, or the shape of the result.

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?

One sentence, front-loaded with the action and target, with zero redundant wording. Nothing could be removed without losing information.

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?

The input side is adequately covered for a one-parameter read-only tool, and annotations cover safety. However, with no output schema, the description never indicates what is returned (e.g. a list of numbers with validity flags), which an agent needs in order to chain this tool's results.

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?

Schema description coverage is 100% and the schema already states maxLength 20000, so the baseline is 3. The description adds a little meaning by narrowing the acceptable content to invoice, receipt or contract text, but repeats the length limit verbatim and adds no format or preprocessing guidance.

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 names specific verbs (find and validate) and specific resources (invoice registration numbers, corporate numbers), and it scopes the operation to free-form document text, which implicitly separates it from the single-value validate_* siblings. It stops short of explicitly contrasting itself with validate_corporate_number or validate_invoice_number.

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 only implied: the phrase 'inside invoice, receipt or contract text' tells an agent this handles batch extraction from a document rather than validating a known ID. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for the single-ID case.

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.