jp-number-grounding
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
After writing a summary or minutes from Japanese text, call jp_number_grounding_check with the source and your summary. Fix or remove every fact it reports as unsupported or unit_mismatch before sending.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jp_number_grounding_checkA | Before you send a summary, meeting minutes (議事録), report or answer written from a Japanese source, pass both texts here. Every number, money amount, percentage, count, date and time in the summary is normalized (三千五百万円 = 3,500万円 = 35,000,000円, 令和7年 = 2025年, R7.4.1 = 2025/4/1, 午後2時 = 14:00, 1割5分 = 15%, 12名 = 12人) and looked up in the source. Returns ok, problems, counts and per-fact status: supported, approx_supported (marked 約/程度 and within tolerance), year_unverified, unit_unverified, unit_mismatch (30人 vs 30件), unsupported (not in the source: often an invented deadline or a wrong figure). Also flags a weekday that does not match its date (W_WEEKDAY_MISMATCH). Deterministic, offline. It checks presence of values, not meaning. 要約の数字・日付・金額が原文にあるかを確かめる。 |
| jp_number_extractA | List every quantity in a Japanese text with its normalized value: kanji numerals, 万/億 units, full-width digits, Japanese era years (令和/平成/昭和, R7), dates, 午前/午後 times, 割/分 rates, counters (人, 名, 件, 社, 回, か月 ...). Skips words that only look like numbers (一宮, 統一, 一部, 万一). Returns facts with kind, text, normalized, value, unit, approx, issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one extracts and normalizes quantities, while the other verifies a summary against a source. Despite sharing normalization logic, their boundaries are explicit and an agent can select correctly without ambiguity.
Both names follow the same predictable pattern: jp_number_ + action. The shared prefix communicates scope, and extract/check are consistent verb choices.
Two tools is slightly below the typical 3-15 range, but the server's scope is narrow and both tools earn their place. A third tool is not obviously needed for extraction and verification workflows.
The surface covers the core lifecycle for this domain: extracting normalized facts and checking a summary against a source. Minor gaps exist around semantic verification and batch workflows, but the presence-only limitation is explicitly stated and agents can work around it.