Skip to main content
Glama

Antigravity x402 & MCP Gateway

audit_uk_property_postcode

[0.006000 USDC via x402] Audits any UK property postcode across ONS/Postcodes.io administrative boundaries, UK Environment Agency nearby 3km river/coastal flood zones, and UK Home Office Police street-level crime incidents by category.

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

Input Schema

NameRequiredDescriptionDefault
postcodeYesValid United Kingdom postcode (e.g., 'SW1A 1AA', 'E14 5AB', 'M1 1AE').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.006000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the paid x402 model and price up front plus the concrete geographic scope (3km flood buffer) — useful behavioral context. It does not disclose what the response looks like (per-domain objects? aggregate risk score?), partial-failure behavior when one upstream source fails, or whether the audit is cached/read-only. Adequate but leaves notable gaps for a paid multi-source aggregator.

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?

One sentence with zero filler; every clause (price, verb, three data domains) earns its place. Front-loading the bracketed pricing ahead of the purpose slightly delays the core action, which keeps it from a 5.

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?

For a paid tool with no annotations and no output schema, the description names the sources but never characterizes the returned artifact — shape, whether domains are scored or listed, or how failures surface. An agent knows what to send but not what it will get back, which is the main completeness gap.

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 both parameters are documented, including examples and the payment-signature semantics, so baseline would be 3. The description adds real meaning by framing the postcode as 'any UK property postcode' (scope: UK-only) and by tying the price prefix to the optional payment flow. It slightly undersells the quote-fallback behavior, which lives only in the schema.

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?

States a specific verb ('Audits') plus a precise resource ('any UK property postcode') and enumerates the three data domains covered: ONS/Postcodes.io boundaries, EA 3km flood zones, and Home Office street-level crime by category. This is unmistakably distinct from every listed sibling (domain security, FDIC health, OFAC screening, etc.), so an agent can select it without opening the schema.

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 by the enumerated data domains — an agent can infer it should call this for UK property due-diligence questions. However, there is no explicit when-to-use/when-not guidance, no statement about preconditions (e.g., UK-only valid postcodes, non-UK rejection behavior), and no named alternative for related postcode/location questions. The 0.006 USDC cost note at least signals a paid call worth reserving for real audits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.