Skip to main content
Glama
nta-invoice-mcp

nta-invoice-mcp

by koizumikento

get_invoice_registration_history

Read-onlyIdempotent

Retrieve published registration, cancellation, and expiry history for a single Japanese invoice registration number to verify status changes over time.

Instructions

Read published registration, cancellation and expiry history for one number.

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>"
    },
    "name": "get_invoice_registration_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
registration_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still contributes real behavioral information by disclosing that only "published" records are returned and that the result covers three event types (registration, cancellation, expiry) — an agent would not know the unpublished-record exclusion from annotations alone. Pagination or ordering for long histories is not addressed.

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 scope qualifier ("published") and cardinality ("one number") are packed into minimal text.

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 one-parameter read tool with annotations and an output schema, so return values need not be explained. The definition covers purpose, record-state scope and event types; the only notable gap is how it relates to the two lookup siblings.

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?

Only one parameter exists and the schema already documents it with a title and regex pattern (^T[0-9]{13}$). The phrase "for one number" reinforces that it targets a single registration rather than a list, but adds no format or sourcing detail beyond the 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 states a specific verb ("Read") and a specific resource ("registration, cancellation and expiry history"), and scopes it to "one number." It is clear enough to distinguish this from a current-status lookup, though it never explicitly contrasts itself with the sibling lookup tools.

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 word "history" suggests a longitudinal/audit use case rather than a point-in-time status check, and "published" hints at a record-state filter. There is no explicit statement of when to prefer this over lookup_invoice_registration or lookup_invoice_registrations, and no prerequisites are given.

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