Skip to main content
Glama

Preview a property data lookup

spur_plan_property_data
Read-onlyIdempotent

Show which providers Spur would use to fill the requested fields of a saved property, which stored values would be reused for free, and what it would cost. Makes no paid call. Always run this and show the user the result before spur_refresh_property_data.

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>",
      "data_points": "<data_points>"
    },
    "name": "spur_plan_property_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectionsNo
data_pointsYes
property_idYes
cross_validateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the important commercial fact that it "Makes no paid call," which annotations cannot express. It stops short of describing the shape of the returned plan or any failure modes, so not a full 5.

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 what is shown, followed by the cost-safety guarantee and the sequencing rule. No filler or restated title.

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

Completeness3/5

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

Absent an output schema, the description does reasonably describe what the result contains (providers, free reuse, cost), which is the core need for a preview tool. However, the nested selections parameter with its mode/fallback options is left entirely unexplained, which is a real gap for a 4-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, including a nested selections object with mode enums (automatic/preferred/locked), providers, allowFallback, fallbackPolicy, plus cross_validate and property_id. The description only alludes to "requested fields" and stored values, leaving the selections semantics and cross_validate undocumented in either place.

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 concrete verb and resource ("Show which providers Spur would use to fill the requested fields of a saved property") and enumerates the three outputs: providers, free reused values, and cost. It also explicitly contrasts with spur_refresh_property_data, so an agent can separate the preview from the paid call.

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 an explicit directive: "Always run this and show the user the result before spur_refresh_property_data." That names the alternative tool and the condition that selects it, covering the main decision an agent faces here.

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