Skip to main content
Glama
nta-invoice-mcp

nta-invoice-mcp

by koizumikento

lookup_invoice_registrations

Read-onlyIdempotent

Check the registration status of up to ten Japanese invoice registration numbers for a specified date to confirm valid invoice issuers.

Instructions

Look up up to ten Japanese invoice registration numbers on one 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_numbers": "<registration_numbers>",
      "day": "<day>"
    },
    "name": "lookup_invoice_registrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
registration_numbersYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds the ten-number batch cap and single-date constraint, but does not explain error handling or result behavior beyond what the output schema provides.

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 definition is a single front-loaded sentence with no wasted wording. The batch limit and date constraint are presented together efficiently.

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?

This is a simple read-only lookup with an output schema and strong annotations covering safety and idempotency. The only notable gap is explicit routing to the singular or history alternatives, but the operational essentials for calling the tool are present.

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 0%, so the description must compensate. It identifies the numbers as Japanese invoice registration numbers and the day as a single YYYY-MM-DD date with a ten-item limit, but it does not explain the T-prefix format, where numbers come from, or richer per-parameter meaning.

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 states a specific verb ('look up'), resource ('Japanese invoice registration numbers'), and batch scope ('up to ten ... on one date'). It implicitly distinguishes itself from the singular sibling by batch size, though it does not name alternatives.

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?

There is no explicit when-to-use, when-not, or alternative guidance. An agent must infer that this is for batch lookups versus the singular or history siblings from the name and the phrase 'up to ten'.

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