Skip to main content
Glama

Get property data with sources

spur_get_property_sources
Read-onlyIdempotent

Read a saved property's data with the source beside every value: which provider supplied it, when, how it was selected, whether it is a fallback or a calculation, and which fields are still unknown. Free, makes no paid lookups.

Always tell the user the source of any number you repeat (e.g. "Estimated value $505,000 from RealEstateAPI, retrieved Nov 3"). Calculated values such as estimated equity are Spur's calculation from the listed inputs, never one provider's figure. Unknown means Spur has no value; never present it as zero.

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": {
      "property_id": "<property_id>"
    },
    "name": "spur_get_property_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_pointsNoLimit to these data points; omit for everything
property_idYesSaved Spur property id
reveal_contactsNoExplicitly reveal restricted contact values; backend permissions and reveal audit apply

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description goes well beyond them: cost profile (free, no paid lookups), what each returned value carries (provider, retrieval time, selection method), what a fallback or calculation means, and that 'unknown' is not zero. That last point prevents a real class of downstream error.

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 core action and cost, then a short presentation paragraph. Every sentence carries weight, though the second paragraph is output-usage guidance rather than tool behavior and could be trimmed slightly.

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 usefully characterizes the return shape (per-value provenance, fallback/calculation flags, unknown fields) and the cost model. It leaves out what the response envelope looks like and how the 60-data-point limit behaves, which is acceptable given the schema documents the cap.

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 100% and all three parameters are self-documented, including the data-point key pattern and the contact reveal audit. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Read a saved property's data') and immediately qualifies the payload ('with the source beside every value'), which is more precise than a generic property-get. It does not name or contrast with siblings such as spur_get_property or spur_get_field_sources, so an agent must infer the difference.

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?

'Free, makes no paid lookups' gives a clear selection signal that steers the agent here instead of the paid refresh/plan tools, and 'saved property' implies the property must already exist. There is no explicit when-not or named alternative, so the routing is implied rather than spelled out.

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