L50 UK Data API

property flood

property_flood

Read-only

Flood risk for one full UK postcode (England): Environment Agency flood warning areas within 1 km with their rivers or sea, and any flood warnings in force within 3 km right now. Costs $0.01 per call, paid in USDC on Base with x402.

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": {
      "postcode": "<postcode>"
    },
    "name": "property_flood"
  }
}

Input Schema

Name	Required	Description	Default
`postcode`	Yes	Full UK postcode, e.g. BS9 1AA

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds genuinely new context: a $0.01 per-call charge paid in USDC on Base via x402, the 1 km / 3 km search radii, and the England-only coverage boundary. It does not describe output shape or what happens for an unmatched postcode, which keeps it short of a 5.

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?

Two sentences, both earning their place: the first delivers purpose plus geographic and radius scope, the second delivers the pricing model. Nothing is repeated from the schema and the most decision-relevant facts come first.

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 one-parameter, read-only lookup with no output schema, the description covers the key decision factors an agent needs — cost, coverage geography, input strictness, and what data is returned. It stops short of describing response structure or behavior on invalid/out-of-scope postcodes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already carries an example, so the baseline is 3. The description adds real meaning beyond that: the postcode must be a *full* postcode, not a district or partial, and must be in England — constraints the schema does not express.

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 names a specific verb+resource (flood risk for a single full UK postcode) and pins down the exact data returned: Environment Agency flood warning areas within 1 km with their rivers or sea, plus live warnings within 3 km. It is unambiguous about scope, though it never contrasts itself with the property_* siblings, so an agent must infer the boundary on its own.

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?

Usage is implied rather than stated: 'one full UK postcode (England)' and 'right now' signal when the tool applies, and the England-only geographic limit is a useful exclusion. There is no explicit when-to-use vs. alternatives guidance and no prerequisites or failure conditions are described.

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

All L50 UK Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?