Skip to main content
Glama

List saved properties

spur_list_saved_properties
Read-onlyIdempotent

List properties the user has saved in Spur, optionally filtered by city, state, list, or enrichment status. Shows cards and a map.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, e.g. "Austin"
limitNoMaximum number of items to return
queryNo
stateNoTwo-letter state, e.g. "TX"
offsetNoNumber of items to skip, for pagination
list_idNoOnly properties in this property list
has_ownerNo
max_priceNoMaximum price in USD (rent per month for rentals)
max_valueNo
min_priceNoMinimum price in USD (rent per month for rentals)
min_valueNo
added_afterNo
property_typeNo
listing_statusNo
enrichment_statusNoSkip-trace status of the property's owner (spur_enrich)
event_within_daysNo
latest_event_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / added_after
      Added value: +{
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / event_within_days
      Added value: +{
      +  "maximum": 3650,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / has_owner
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / latest_event_types
      Added value: +{
      +  "items": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "maxItems": 30,
      +  "type": "array"
      +}
    • addedInput schema / properties / listing_status
      Added value: +{
      +  "enum": [
      +    "forRent",
      +    "forSale",
      +    "sold",
      +    "none"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / max_value
      Added value: +{
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / min_value
      Added value: +{
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / property_type
      Added value: +{
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds 'Shows cards and a map', which hints at a UI/visualization result but is ambiguous for an API consumer. It omits useful behavior such as pagination defaults (limit=20, offset) and what happens when no filters are supplied.

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 tight sentences with the core purpose front-loaded and no filler. The trailing 'Shows cards and a map' is the only questionable sentence, being UI-flavored rather than operationally useful.

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?

For a 17-parameter tool with no output schema, the description is thin: it does not explain pagination, filter combination semantics, or the price versus value distinction. An agent would have to rely on the partially documented schema to call this 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?

Only 4 of 17 parameters (city, state, list_id, enrichment_status) are echoed in the description, matching schema coverage of roughly 47%. Several ambiguous parameters remain undocumented anywhere, notably min_value vs min_price, max_value, query, has_owner, property_type, added_after, event_within_days and latest_event_types, so the description fails to compensate for the coverage gap.

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 states a specific verb and resource ('List properties the user has saved in Spur') and implies a saved-set scope that distinguishes it from the search sibling, even though no sibling is named explicitly. An agent knows this returns the user's saved properties, not a fresh search.

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?

Usage is implied by 'properties the user has saved' and the example filters, so an agent can infer this is a browse/list operation. However, there is no explicit when-to-use guidance, no mention of quando to prefer spur_search_properties instead, and no note that all filters are optional.

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