Skip to main content
Glama

Property timelines and recent events

spur_get_property_events
Read-onlyIdempotent

Read an individual property's event history, recent portfolio events, or the event-type catalog. Free. Event dates and detection dates are distinct.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisNoevent
limitNo
typesNo
catalogNo
property_idNo
within_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond that: the tool is free and event dates versus detection dates are meaningfully distinct. It does not explain pagination, ordering, or return shape, so the added behavioral context is helpful but not rich.

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?

The description is three short sentences and front-loads the core capability. Every element—read modes, free status, and event-vs-detection date distinction—adds information with no filler.

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?

With six parameters, no required parameters, zero schema description coverage, and no output schema, the description is too thin to fully equip an agent. It identifies the main read modes but does not explain most parameters or describe what the returned event history will contain.

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%, so the description must carry parameter meaning. It partially explains the catalog mode and the basis distinction between event and detection dates, but it leaves limit, types, within_days, and property_id semantics largely unaddressed.

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 uses a clear verb ('Read') and resource ('property's event history') and names three distinct modes: individual history, portfolio-level recent events, and the event-type catalog. It does not explicitly distinguish itself from the likely sibling spur_refresh_property_events, so sibling differentiation is present only implicitly through 'Read'.

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 description implies usage by listing scenarios (individual property history, recent portfolio events, catalog lookup) and noting the tool is free. It does not state when to use it versus refreshing events first or when another property-related tool is more appropriate, so guidance remains implied rather than explicit.

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