Skip to main content
Glama
nta-invoice-mcp

nta-invoice-mcp

by koizumikento

lookup_invoice_registration

Read-onlyIdempotent

Look up one Japanese invoice registration number for a specified date (YYYY-MM-DD) to verify its registration status on that day.

Instructions

Look up one Japanese invoice registration number on a specified date (YYYY-MM-DD).

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": {
      "registration_number": "<registration_number>",
      "day": "<day>"
    },
    "name": "lookup_invoice_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
registration_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the lookup is date-scoped and singled-number-only, which is useful behavioral context not in the annotations, but it says nothing about failure behavior (e.g., invalid or unregistered number) or rate limits. With annotations carrying the safety burden, a 3 is appropriate.

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?

A single front-loaded sentence with no filler; the key scoping constraint (one number) and the required date input are both stated immediately. 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 required scalars, output schema present so return values need not be explained, annotations covering safety). The description covers what it does and its singular scope, leaving only minor gaps: no explicit sibling routing and no note on behavior for invalid/nonexistent numbers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it only partially does: it clarifies the date format (YYYY-MM-DD) and that exactly one registration number is supplied. It adds nothing about the T-prefixed 13-digit format, and the YYYY-MM-DD format is already enforced by the schema pattern, so the added meaning is thin for an undocumented two-parameter schema.

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 a specific verb and resource ("look up one Japanese invoice registration number") and distinguishes singular scope from the sibling lookup_invoice_registrations (plural) and get_invoice_registration_history. It does not explicitly name those siblings as alternatives, so it falls short of a 5.

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

Usage Guidelines2/5

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

It states the singular use case and requires a date, but there is no explicit when-to-use versus alternatives guidance: nothing says to use lookup_invoice_registrations for multiple numbers or get_invoice_registration_history for past records. The agent must infer routing from the name alone.

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