Skip to main content
Glama

Fetch property data from providers

spur_refresh_property_data
Destructive

Run the lookup previewed by spur_plan_property_data and return the updated values with their sources. Can spend the user's credits and provider costs. Requires the user's explicit approval of the preview (confirm=true). A provider with no record is never charged and never silently replaced by another one.

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>",
      "confirm": "<confirm>"
    },
    "name": "spur_refresh_property_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
selectionsNo
data_pointsYes
property_idYes
cross_validateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but they cannot convey that the call spends the user's credits and incurs provider costs — the description adds that, plus the 'never charged / never silently replaced' fallback guarantee and the approval gate. It still does not say what happens on partial failure or partial writes across providers, which matters for a destructive, non-idempotent tool.

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?

Four short sentences, front-loaded with the action and its source data, then cost, then the approval gate, then the fallback guarantee. No restated titles or filler, and each sentence carries distinct information.

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?

For a costly, destructive, nested-schema tool with no output schema, the description covers cost, approval, and return shape ('updated values with their sources') but leaves the entire provider-selection semantics undocumented. Adequate to prevent an agent from calling it unapproved, not adequate to configure selections or cross_validate correctly.

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 only 20% across 5 parameters, and the description explains only confirm=true (approval). The nested 'selections' object (mode automatic/preferred/locked, providers, allowFallback, fallbackPolicy) and cross_validate are left entirely to the schema, so the description does not compensate for the coverage gap on the most semantically loaded parameter.

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?

The description opens with a specific verb and pairing: 'Run the lookup previewed by spur_plan_property_data and return the updated values with their sources.' That distinguishes it from the plan sibling (preview) and from generic job runners, and an agent can tell execution from planning without reading either schema.

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 implicitly defines the workflow (plan first, then execute) and states a hard prerequisite: the user's explicit approval of the preview via confirm=true. It stops short of naming when NOT to use it or what to do if the plan is stale or rejected, so there is a small usage gap.

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