Skip to main content
Glama

Find a house

find_house
Read-only

Look up a Vancouver address, a street, a building's name or a resident's surname from 1945 or earlier in AddressLore's coverage. Returns the matching house's path for house_history; the candidates when the address could be on more than one street ("which street") or matches more than one old address; a street's houses a page at a time with its page; or says plainly that the address isn't covered (never a nearby house in its place), with the nearest covered streets and the coverage page.

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

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of a street's houses (40 a page) or of the buildings a word finds; 1 if left out.
queryYesAn address ("526 Keefer Street"), a street ("Keefer Street") or a surname ("Clandenning").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of a street's houses (40 a page) or of the buildings a word finds; 1 if left out.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"An address (\"526 Keefer Street\") or a surname (\"Clandenning\")."New value: +"An address (\"526 Keefer Street\"), a street (\"Keefer Street\") or a surname (\"Clandenning\")."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes well beyond that by explaining each return shape (single path, candidate list for ambiguous addresses, paginated street listing, or an explicit not-covered answer). The explicit promise that it never substitutes a nearby house is exactly the kind of behavioral guarantee an agent cannot infer from annotations.

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 front-loaded sentence states the lookup, followed by the outcome enumeration; nothing is redundant. It is dense and the return-value clause is long, but every clause carries information the agent needs given there is no output schema.

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?

With no output schema, the description carries the full burden of describing return values and does so for all four outcomes, including pagination and the negative-result behavior. Combined with a fully documented two-parameter schema, an agent has enough to call it correctly and interpret the response.

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%, so the baseline is 3, but the description adds meaning by tying query to distinct resolution modes (address ambiguity prompting 'which street', street listing paginated) and by indicating that page applies to street-house and word-match listings. It does not add syntax details beyond the schema's own examples, so not a 5.

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 (look up) and precise resources (address, street, building name, resident surname) with a scope constraint (Vancouver, 1945 or earlier, within AddressLore coverage). It also signals its role as the entry point that yields a path for house_history, so it is distinguishable from that sibling.

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?

It implies the workflow: use this tool to obtain the house path that house_history needs, and it explains what happens when nothing matches (coverage page and nearest covered streets rather than a substitute house). It does not explicitly say when to skip this tool and go straight to house_history or coverage, so it falls short of a full when/when-not statement.

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