Praesago

get_area_context

Read-only

Get area intelligence for a UK postcode district: demographics, income, housing tenure, dwelling types, deprivation (IMD), health, education, broadband, flood risk, council tax, politics, and 12-month property prices.

Instructions

Full area intelligence for a UK postcode district: demographics, income, housing tenure, dwelling types, deprivation (IMD), health, education, broadband, flood risk, council tax, politics, and 12-month property prices. Requires a Praesago API key for full data; returns the score summary otherwise.

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": {
      "area": "<area>"
    },
    "name": "get_area_context"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes	UK postcode district, e.g. "E17"

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds important behavioral context about API key requirements and the fallback behavior (score summary without key), which is not captured by annotations.

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 sentences long, front-loads the purpose with a comprehensive list of outputs, and then states the usage condition. Every sentence adds value without redundancy.

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?

Given no output schema, the description enumerates the wide range of data returned (demographics, income, etc.) and notes the fallback when no API key is provided. This adequately sets expectations, though a structured list or format hint would improve completeness.

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?

The only parameter 'area' is described in the schema as a UK postcode district with an example ('E17'). The description reinforces this usage context, adding value beyond the schema's type definition.

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?

The description clearly states the tool provides 'full area intelligence for a UK postcode district' and lists numerous specific data categories. It distinguishes itself from siblings like 'get_area_score' by implying a more comprehensive result.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that a Praesago API key is needed for full data, otherwise a score summary is returned. This provides clear context on when to use the tool effectively, though it does not explicitly contrast with sibling tools.

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

Deploy Server