Skip to main content
Glama

Save properties

spur_save_properties

Save search results into the user's Spur properties (and optionally a property list). Pass listing objects from spur_search_properties structuredContent.cards[].listing. Free. Already-saved properties are updated, not duplicated.

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": {
      "listings": "<listings>"
    },
    "name": "spur_save_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idNoAlso add the saved properties to this property list (spur_list_property_lists)
listingsYesListing objects copied unchanged from spur_search_properties structuredContent.cards[].listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / listings / items / properties / dataSearch
      Added value: +{
      +  "additionalProperties": {},
      +  "properties": {
      +    "items": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "values": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "values"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / listings / items / properties / resultToken
      Added value: +{
      +  "description": "Signed by Spur at search time; required to save",
      +  "minLength": 10,
      +  "type": "string"
      +}
    • changedInput schema / properties / listings / items / properties / zpid / type
      Previous value: -[
      -  "number",
      -  "string"
      -]New value: +[
      +  "number",
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / listings / items / required
      Previous value: -[
      -  "zpid",
      -  "address"
      -]New value: +[
      +  "resultToken",
      +  "dataSearch",
      +  "address"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: the operation is free (a cost signal the annotations do not carry) and existing saved properties are updated rather than duplicated, which tells the agent dedupe behavior. The upsert wording sits in mild tension with idempotentHint=false but does not contradict it outright, since an update can still mutate record state. It does not describe what happens if resultToken is stale or expired.

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 scope, then the data source, cost, and dedupe behavior. No sentence is padding; even the fragment "Free." carries decision-relevant information.

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

Completeness4/5

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

With only two parameters, full schema coverage, and annotations covering safety, the description supplies what the structured fields cannot: where the listing objects come from, that the call is free, and how duplicates are handled. The remaining gap is failure behavior for invalid or expired resultToken values.

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 100%, so both parameters are already documented in the schema, and the description largely restates the same guidance. It adds no syntax, size limits, or value details beyond what the schema provides, so the baseline of 3 applies.

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 specific verb and resource ("Save search results into the user's Spur properties") and pins the scope to search-derived listings. The parenthetical about optionally targeting a property list and the instruction to pass listing objects from spur_search_properties clearly separate it from manual-entry siblings like spur_add_manual_properties.

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?

The prerequisite is explicit: listings must come from spur_search_properties structuredContent.cards[].listing, and the list_id parameter is tied to spur_list_property_lists. It falls short of a 5 because it never states an exclusion such as when to use spur_add_manual_properties instead, leaving the agent to infer the boundary.

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