Skip to main content
Glama
jshis-mcp

jshis-mcp

by koizumikento

get_earthquake_hazard

Read-onlyIdempotent

Calculate the 30-year probability that a WGS84 latitude/longitude point will meet or exceed a chosen JMA seismic intensity threshold.

Instructions

Read the 30-year probability of meeting or exceeding a JMA intensity at a WGS84 point.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_earthquake_hazard"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYes
longitudeYes
minimum_jma_intensityNo6-lower

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful semantics not in the annotations — the 30-year time horizon, that the value is a probability of exceedance, and the WGS84 coordinate frame — but says nothing about units, return format, or how the probability is computed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause carries information. It is efficient but trimmed so far that it omits the parameter guidance this tool needs.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Still, for a 3-parameter tool with 0% schema descriptions and a defaulted enum parameter, one sentence leaves the agent guessing about intensity thresholds and coordinate units.

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 carry the parameter burden. It only gestures at the parameters: 'WGS84 point' implies latitude/longitude as decimal degrees, and 'JMA intensity' hints at minimum_jma_intensity, but it never mentions the allowed enum values (5-lower through 6-upper) or the 6-lower default, which the schema exposes only as raw constraints.

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?

States a specific verb (Read) and a precise resource: the 30-year probability of meeting or exceeding a JMA intensity at a WGS84 point. That is enough to tell it apart from sibling tools such as get_hazard_intensity or get_surface_ground_amplification, though it never names them explicitly.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over a sibling hazard tool. The only usage signal is implicit in the noun phrase '30-year probability', which the agent must interpret itself.

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