Skip to main content
Glama

One home in detail

home_details
Read-onlyIdempotent

Call this when the buyer picks, compares or asks about a home find_homes returned, before answering about its schools, childcare, who lives nearby, safety, development or sales nearby: find_homes gives only what each home matched. Pass the same answers and the home's id. Returns its facts, school zones and nearest schools, childcare in its suburb, who lives nearby, recorded crime, development applications nearby and recent sales nearby.

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": {
      "profile": "<profile>",
      "id": "<id>"
    },
    "name": "home_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a home find_homes returned for the same answers.
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / profile / properties / ideal
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "text": {
      -      "anyOf": [
      -        {
      -          "maxLength": 600,
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "The buyer's own words about the home they want. Kept as written; it changes no verdict. Leave it out unless the buyer said it."
      -    }
      -  },
      -  "type": "object"
      -}
  2. Changed5 schema fields changed
    • changedInput schema / properties / profile / properties / commute / properties / arriveBy / description
      Previous value: -"The time to arrive by, 24-hour \"HH:MM\". Leave it out unless the buyer said it."New value: +"The time to arrive by, 24-hour \"HH:MM\". Needed for the public transport trip to be checked. Leave it out unless the buyer said it."
    • changedInput schema / properties / profile / properties / commute / properties / maxMinutes / description
      Previous value: -"The longest the trip may take, in minutes. Only a public transport (\"Transit\") trip rules homes out. Leave it out unless the buyer said it."New value: +"The longest the trip may take, in minutes. Only a public transport (\"Transit\") trip rules homes out. Needed for the public transport trip to be checked. Leave it out unless the buyer said it."
    • changedInput schema / properties / profile / properties / commute / properties / mode / description
      Previous value: -"How the buyer travels. A driving or cycling trip is not checked here and rules nothing out. Leave it out unless the buyer said it."New value: +"How the buyer travels. A driving or cycling trip is not checked here and rules nothing out. Needed for the public transport trip to be checked. Leave it out unless the buyer said it."
    • changedInput schema / properties / profile / properties / schools / properties / travelTo / description
      Previous value: -"Kinds of school the buyer wants nearby. With schools.within set, a home with none that close is ruled out. Leave it out unless the buyer said it."New value: +"Kinds of school the buyer wants nearby. With schools.within set, a home with none that close is ruled out. Needs schools.within for the distance to be checked. Leave it out unless the buyer said it."
    • changedInput schema / properties / profile / properties / schools / properties / within / description
      Previous value: -"How far, in a straight line, the nearest school of a kind in schools.travelTo may be. Leave it out unless the buyer said it."New value: +"How far, in a straight line, the nearest school of a kind in schools.travelTo may be. Needs schools.travelTo for the distance to be checked. Leave it out unless the buyer said it."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds the non-obvious rule that the profile must be 'the same answers' used for find_homes, plus a full enumeration of what the response contains. It does not state what happens with a stale or foreign id, which is the remaining gap.

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?

Front-loaded with the trigger, then the constraint, then the return payload — a sensible order with no filler. It is dense and runs long in a single breath, but every clause (trigger, find_homes contrast, passthrough rule, return list) carries distinct information.

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 must — and does — enumerate the returned detail categories, and it explains the two-parameter contract. For a read-only lookup of this shape, the only thing missing is failure behavior for an unknown or mismatched id.

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 partial (50%) and the nested profile object carries much of its own documentation, but the description adds the essential semantic the schema cannot express: the profile is a passthrough of the find_homes profile and must be identical. The 'home's id' phrasing ties the id to a prior find_homes result, preventing fabricated ids.

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+resource pair ('home_details' returns one home's full detail) and explicitly contrasts it with find_homes ('find_homes gives only what each home matched'). The list of what comes back — school zones, childcare, nearby residents, crime, development applications, recent sales — makes the tool's scope unmistakable without opening the schema.

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?

Gives a precise trigger ('when the buyer picks, compares or asks about a home find_homes returned'), a timing constraint ('before answering about its schools, childcare...'), and names the alternative it is not for. An agent knows exactly when to escalate from find_homes to home_details.

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