Skip to main content
Glama

Update saved property

spur_update_property
Destructive

Edit saved property fields, correct manually entered owner contacts, or soft-delete a property. Manual corrections are user-supplied facts and make no paid lookup.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds two pieces of context those annotations cannot convey: the delete is a *soft* delete rather than a hard purge, and the contact-correction path performs no paid lookup (no credit spend). It does not discuss reversibility of the soft delete or whether contact corrections overwrite existing values, which would have pushed this higher.

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?

Two sentences, no filler, and the three primary operations are front-loaded ahead of the qualifying note about paid lookups. Every clause carries information an agent needs.

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?

For a three-branch mutation tool whose schema and annotations already cover the safety profile and per-field constraints, the description supplies the missing semantic layer (intent-to-action mapping, soft-delete nature, no-cost corrections). The main residual gap is the absence of any note on partial-update behavior for the changes object, which matters for a non-idempotent write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the oneOf branches are self-documenting, but the description still adds meaning by mapping each action discriminator to its real-world intent (field edit vs. manual contact correction vs. delete), which helps the agent pick the right branch before reading constraints. It adds no detail about the individual editable fields, which is acceptable given the schema already covers them.

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-and-resource pair ('Edit saved property fields') and enumerates the three distinct operations the tool supports: field edits, manual owner-contact corrections, and soft-delete. An agent can tell this is the mutation counterpart to the read-oriented property tools, though no sibling is named explicitly.

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 the enumeration of the three modes, and 'Manual corrections are user-supplied facts and make no paid lookup' hints at when to prefer this over paid data-refresh tools. However, it never explicitly states 'use X instead for paid lookups' or warns when NOT to use the delete branch, leaving the agent to infer routing.

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