Skip to main content
Glama

Area facts

area_facts
Read-onlyIdempotent

Use this for what an area is like around a new home, a development or a place: sold house prices nearby, flood and other risks, crime per 1,000 residents against the council, road and rail noise against the WHO guidelines, broadband and full fibre, indoor mobile signal, air quality, the nearest schools with their Ofsted judgement, shops, parks, GP and station distances, walk and transit scores, local pay and jobs, or the journey time by road or on foot to a place (journey_to). Returns only the measures asked for. Describes places, never who lives there. Schools are held for England only.

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": {
      "measures": "<measures>"
    },
    "name": "area_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNoA home or development page address from a search. Give this or place.
modeNodrive
placeNoA town, postcode district or full postcode, when no home is named.
measuresYes
journey_toNoA place to time the journey to from a home: a town, station or postcode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuinely new behavioral facts: output is restricted to the requested measures, the data describes places rather than residents (a privacy/scope constraint), and school data coverage is limited to England — a material limitation an agent would otherwise only discover from empty results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage cue is front-loaded, which is good, but the core is one very long run-on sentence whose measure enumeration largely restates the schema enum. The three short trailing sentences ('Returns only the measures asked for', 'Describes places, never who lives there', 'Schools are held for England only') are the highest-value lines and could have been given more prominence.

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?

With no output schema, the description does the right work by stating that only requested measures are returned and noting the England-only school limitation. For a five-parameter read tool this is nearly sufficient; the remaining gap is the unexplained 'mode' parameter and the absence of any hint about result shape or units for measures like noise or crime rates.

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 coverage is 60%, and the description clarifies journey_to as a travel-time destination from a home, which is useful. But the 'mode' parameter (drive/walk/transit enum) is never mentioned in either the description or the schema, and the relationship between home, place and journey_to is only partially implied — the long measure list duplicates the measures enum without adding meaning.

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 concretely enumerates the resource: sold prices, risks, crime rates, noise vs WHO guidelines, broadband, mobile signal, air quality, schools with Ofsted, amenities, scores, pay/jobs, and journey times. That is far more specific than the title and clearly separates it from search_homes or find_schools, but there is no crisp verb — 'Use this for what an area is like' leaves the agent to infer that it retrieves a report rather than searching or computing.

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?

It gives usage contexts ('around a new home, a development or a place') and flags one specific mode of use (journey_to for travel time), which implies when to call it. However, there are no exclusions or pointers to siblings — an agent cannot tell from this whether to use area_facts or find_schools for school information, or how this relates to get_home.

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.

Resources