Skip to main content
Glama

Get property

spur_get_property
Read-onlyIdempotent

Show one saved Spur property as a detailed card by property_id, with owner links and enrichment status. (zpid lookups were removed; save a listing first.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spur_get_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
zpidNoDeprecated: no longer supported
property_idNoSaved Spur property id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / zpid / description
      Previous value: -"Zillow property id from search results"New value: +"Deprecated: no longer supported"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by previewing what comes back (owner links, enrichment status) and by disclosing the removal of zpid lookups, which is a behavioral change not visible in the annotations. It stops short of mentioning what happens when the id is unknown or whether enrichment may be stale.

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?

Two sentences, front-loaded with the core action and keyed parameter, and the parenthetical carries the one caveat that matters. Nothing is padded or restated from the title.

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?

For a single-record read with full annotation coverage and a fully described two-parameter schema, this covers the essentials: what it returns, how it is keyed, and what no longer works. With no output schema, a brief note on the miss/failure case would make it complete.

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%, so the schema already documents property_id as the saved Spur property id and labels zpid as deprecated and unsupported. The description merely echoes that by saying lookups are keyed by property_id and that zpid was removed, adding no format, sourcing, or fallback detail beyond the structured fields.

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 gives a specific verb and resource ("Show one saved Spur property") plus the keying parameter (property_id) and the shape of the response (a detailed card with owner links and enrichment status). It implicitly separates this general card view from the domain-specific siblings (dnc, events, sources, stats) without naming any of them, which keeps it just short of a 5.

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?

The parenthetical establishes a real prerequisite: only saved properties can be looked up, and zpid-based lookups no longer work. That is useful when-to-use context, but there is no explicit routing to sibling tools such as spur_get_property_events or spur_get_property_stats for the narrower data views.

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