Skip to main content
Glama
location-risk-mcp

location-risk-mcp

Summarise risk context

summarise_risk_context
Read-onlyIdempotent

Generates a rule-based pre-screen summary for homeowners property risk, covering overall level, severity-ranked flags with evidence, follow-up questions, and data gaps.

Instructions

Rule-based pre-screen summary: an overall level, flags ranked by severity with the evidence each one rests on, suggested follow-up questions, and data gaps.

Calls enrich_location itself if needed. Decision support only, not an underwriting decision.

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": "summarise_risk_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
location_idYes
line_of_businessNohomeowners

Output Schema

NameRequiredDescriptionDefault
gapsYes
flagsYes
disclaimerYes
location_idYes
data_sourcesYes
overall_levelYes
ruleset_versionYes
line_of_businessYes
formatted_addressYes
refer_to_underwriterYesTrue when any flag is high, or core data is missing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses the internal dependency on enrich_location, that the logic is rule-based (so output is deterministic and explainable rather than model-generated), and that results are advisory only. The main gap is not stating what happens when enrichment fails or when data is too sparse to score.

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?

Three short sentences, front-loaded with what the tool returns, then the internal-call note, then the disclaimer. No filler, though the output enumeration slightly overlaps with the existing output schema.

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?

For a two-parameter, read-only tool with an output schema already documenting return shape, the description covers purpose, hidden dependency, and usage caveat adequately. The remaining hole is the undocumented line_of_business scope restriction and ID expectations, which matter for correct invocation.

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 carries the full burden, yet it never mentions either parameter. It says nothing about what a location_id must be (canonical ID vs. raw address, whether standardise_address is a prerequisite) and never mentions line_of_business, whose homeowners-only constraint is only visible as a schema 'const'.

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 and resource ('Rule-based pre-screen summary') and enumerates the payload: overall level, severity-ranked flags with evidence, follow-up questions, and data gaps. It also distinguishes itself from the enrich_location sibling by noting it performs that call internally, so an agent can tell it does not need to chain manually.

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?

'Calls enrich_location itself if needed' implicitly tells the agent not to pre-enrich, which is real routing guidance, and 'Decision support only, not an underwriting decision' scopes the output's use. However, there is no explicit 'use this when...' trigger, no statement of when to prefer raw enrichment over this summary, and no cost/latency expectations for a tool that fans out to another call.

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