Skip to main content
Glama

Refresh property timeline

spur_refresh_property_events
Destructive

Fetch current listing/record events. Can spend data credits; approve the selected sources first.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, open-world, non-idempotent, destructive operation, so the description is not the sole bearer. It still earns credit for two facts not encoded in annotations: that the call can consume data credits, and that source selection must be user-approved beforehand. The gap is that destructiveHint=true is never explained — the agent is not told whether a refresh overwrites or duplicates existing events.

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?

Two short sentences with no filler, and the credit-spend warning is front-loaded in second position where it matters most. The phrasing 'approve the selected sources first' is terse to the point of ambiguity — it is not obvious that this means setting confirm=true.

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

Completeness2/5

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

This is a destructive, credit-spending, non-idempotent mutation with three required parameters, no output schema, and low schema coverage — a case where the description should carry more. Key facts are missing: roughly what a refresh costs, whether existing event data is replaced, expected latency, and what the response contains.

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 only 33% (only 'confirm' is documented), so the description should compensate and only partly does. 'Approve the selected sources first' maps the 'sources' parameter to an approval flow, and the credit-spend warning implies cost varies by source, but neither 'zillow' nor 'records' is explained, nor is which source is more expensive or slower.

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 names a specific verb-plus-resource ('Fetch current listing/record events'), and 'current' hints at a fresh pull versus the cached sibling spur_get_property_events. However, it never names or fences off that sibling, so the agent must infer the difference from the name alone rather than from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance: nothing tells the agent to prefer this over spur_get_property_events or spur_refresh_property_data, and no conditions under which it should be avoided. The only conditional text ('approve the selected sources first') is a prerequisite for this tool, not a routing rule between tools.

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