Skip to main content
Glama
Sign In
nankai-trough-mcp

nankai-trough-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Nankai Trough Scale & Reach

nankai_overview
Read-onlyIdempotent

Get cited official 2025 Nankai Trough quake estimates: probability, worst-case casualties, intensity-7 reach, tsunami. Start here before address-specific hazard maps.

Instructions

Get the headline facts of the official 2025 Nankai Trough estimate (probability, worst-case casualties/loss, intensity-7 reach, tsunami) with sources. Start here to understand the scale; then call official_hazard_maps for a specific address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nankai_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOutput language: 'en', 'ja', or 'both' (default).both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the tool provides sources and is an overview, but does not disclose additional behavioral traits such as response format, pagination, or any caveats. It does not contradict annotations, but adds limited behavioral context beyond them.

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 description is two sentences long, front-loaded with the primary result and a clear usage pointer. Every sentence earns its place: the first explains what the tool returns, the second explains when and how to proceed. No redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

There is no output schema, so the description must convey the return value. It lists the key facts (probability, casualties, intensity-7 reach, tsunami) and mentions 'with sources', giving the agent a clear expectation. For a simple overview tool with one optional parameter and strong annotations, this is sufficiently complete.

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?

The schema provides 100% coverage for the single 'language' parameter with an enum and description. The tool description does not add any additional parameter semantics beyond what the schema already conveys, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'get' and identifies the resource as 'headline facts of the official 2025 Nankai Trough estimate', listing the content areas (probability, casualties, intensity-7 reach, tsunami) and sources. It clearly distinguishes itself from sibling tools by positioning as the starting point and even pointing to the next tool to call.

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

Usage Guidelines5/5

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

The description explicitly states when to use it: 'Start here to understand the scale' and then instructs to call official_hazard_maps for a specific address. This provides clear usage context, a sequential workflow, and an alternative tool for a different use case.

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

Deploy Server

Other Tools