Praesago

search

Read-only

Find UK property area intelligence by entering a place name, region, or postcode district. Returns matching areas with trajectory scores and links.

Instructions

Search Praesago UK property area intelligence by place name, region or postcode district. Returns matching areas with trajectory scores and links.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Place name, region or postcode district

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it 'returns matching areas with trajectory scores and links', which provides behavioral context beyond annotations. However, it does not disclose any additional behaviors like pagination or result limits.

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 a single sentence that front-loads the action and outcome. No wasted words; every part is meaningful and concise.

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 the tool's simplicity (one parameter, no output schema, no nested objects), the description covers the search scope and return type. It does not specify response format or result count, but those are partially inferable from the domain. Nearly complete for a straightforward tool.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, so baseline is 3. The description's phrase 'by place name, region or postcode district' reinforces the schema description without adding new semantics. No additional parameter-level details are provided.

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 uses specific verb 'Search' and resource 'Praesago UK property area intelligence', and details the types of input (place name, region, postcode district). It clearly distinguishes the tool's purpose from generic search, but lacks explicit differentiation from sibling 'search_areas'. However, the specificity is sufficient for a high score.

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?

No guidance on when to use this tool versus alternatives like 'search_areas' or 'get_area_score'. The description does not mention any exclusions or preferred contexts, leaving the agent without decision framework.

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

Deploy Server