Skip to main content
Glama
location-risk-mcp

location-risk-mcp

Enrich location

enrich_location
Read-onlyIdempotent

Adds hazard and property context to a standardized location: flood zone proximity, wildfire band, earthquake exposure, crime index, fire station drive distance, and building attributes, with gaps listed rather than estimated.

Instructions

Hazard and property context for a standardised location: flood zone and distance to the 100-year zone, wildfire band, earthquake exposure, crime index, fire station drive distance, and building attributes (no owner or sale data).

Each block has its own source. Anything unavailable is listed in gaps, never estimated.

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": {
      "location_id": "<location_id>"
    },
    "name": "enrich_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
location_idYes

Output Schema

NameRequiredDescriptionDefault
gapsNo
crimeNo
floodNo
propertyNo
wildfireNo
earthquakeNo
location_idYes
fire_protectionNo
formatted_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, and closed-world behavior, while the description adds meaningful context about per-block sourcing and missing-data handling. It explicitly states that unavailable data is listed in gaps and never estimated, which helps the agent understand output reliability.

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 focused sentences that front-load the resource and data blocks before explaining source and gap behavior. Every sentence carries useful information without unnecessary repetition.

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?

Because an output schema exists, the description does not need to detail return values, and it covers the main behavioral caveats around data sources and gaps. It remains somewhat incomplete on parameter usage and sibling differentiation, but it is largely sufficient for calling the tool correctly.

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% and there is one required parameter, location_id, whose format or origin is not explained. The description only says the tool works on a 'standardised location', which hints at the expected input but does not compensate for the missing parameter documentation.

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 clearly states the tool returns hazard and property context for a standardised location, and it lists the specific data blocks included. It does not explicitly differentiate from siblings such as summarise_risk_context, so it falls short of a 5.

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?

The description implies the input must be a standardised location, but it gives no explicit when-to-use guidance or comparison against alternatives. It does not state when to use enrich_location versus summarise_risk_context or standardise_address.

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