MarketCode

Search assets, completed sales, planning and market profiles

search_entities

Read-onlyIdempotent

Bounded public search using the versioned SearchQuery. Criteria are validated by the server; sorting and pagination use the same eligibility as the map. All Entities returns separate groups. No graph inference or unknown evidence changes eligibility.

QUERY SHAPE — `query` is one object:
  {"entity": "land",
   "geography": {"kind": "area", "id": "Kettering"},
   "criteria": {"parcel_area": {"min": 5000, "max": 9000}},
   "sort": "<a sort key>"}
`geography` is {"kind": "area", "id": <area UUID, code or exact name>} or {"kind": "polygon", "geometry": <GeoJSON Polygon>}. Refinements go in `criteria`, an object keyed by refinement (not a list, not `filters`/`refinements`). `limit` and `cursor` are arguments of this tool, not of the query.

Families (`query.entity`): Assets — `properties`, `buildings`, `land`, `listings`; Activity — `transactions` (HM Land Registry completed sales matched to a property) and `planning_applications` (official publishers only); Markets — `market_profiles` (one record per area × residential bedroom cohort with the selected `measure`'s latest value and observed trend; open one with `market_profile`). `market_facts` remains for existing observation ids but is superseded by `market_profiles`. Call `entity_search_capabilities` for each family's refinements and sorts. Free.. Actors — `owners` (companies that own homes in the place, ranked by holdings; companies only, signed-in account required, not the shared preview) and `agents` (estate and letting agents by listing activity in a trailing window). Owners and agents are searched on their own, not inside All Entities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`cursor`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive, and the description goes well beyond them: criteria are server-validated, sorting and pagination share the map's eligibility rules, no graph inference or unknown evidence alters eligibility, All Entities returns separate groups, and owners exclude anonymous preview. That is meaningful behavioral context an annotation cannot express.

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?

Long but justified by a ten-family tool; the single-sentence opening and the dedicated QUERY SHAPE block make it front-loaded and scannable. Minor cost: cramped phrasing such as the garbled 'Free.. Actors' line and dense enumeration slightly reduce readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be described, and for a high-complexity multi-family search the description supplies the family taxonomy, geography forms, criteria conventions, and the capability-discovery next step. Nothing an agent needs to invoke it correctly is missing.

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?

Top-level schema descriptions are empty (0% coverage), so the description carries the load and does so well: the full query shape, the 'area' vs 'polygon' geography forms, the correct 'criteria' object shape with range/choice/date-range conventions, and the warning that it is not a list nor 'filters'/'refinements'. It only falls short on `limit` and `cursor`, which are named but not explained (default, pagination semantics).

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 (search) and resource (entities across named families), and enumerates every family with a plain-language gloss (e.g. 'transactions (HM Land Registry completed sales matched to a property)', 'market_profiles (one record per area × residential bedroom cohort...'). An agent can tell what each family yields without opening the schema, and it distinguishes itself from siblings like market_profile and entity_search_capabilities.

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

Usage Guidelines5/5

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

Explicit routing: 'Call entity_search_capabilities for each family's refinements and sorts', 'open one with market_profile', 'market_facts ... is superseded by market_profiles', and 'Owners and agents are searched on their own, not inside All Entities'. It also states preconditions (signed-in account required, not the shared preview) and the when-not for All Entities.

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

All MarketCode 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?