Ferret

Add or change a property

save_property

Adds a property — a home, vacation home, rental, storage unit or vehicle, the top level of where things are kept — or, with id, changes one (rename, kind, address, year built, value, notes).

Instructions

Adds a property — a home, vacation home, rental, storage unit or vehicle, the top level of where things are kept — or, with id, changes one (rename, kind, address, year built, value, notes). To add: only name is needed (type defaults to home); check list_locations first so you don't add one twice. To change: fields left out stay as they are; null clears one. Rooms, closets and shelves inside it are save_location. Returns the property with its id.

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": "save_property"
  }
}

Input Schema

Name	Required	Description
`id`	No	The property to change, from list_locations; leave out to add a new one
`city`	No	Town or city
`name`	No	What the household calls it: "Home", "Lake cabin", "Storage unit 12"
`type`	No	What kind of property it is
`notes`	No	Anything else worth keeping about it
`region`	No	State, province or region
`street`	No	Street address (used for its map picture, if maps are on)
`country`	No	Country name
`yearBuilt`	No	The year the building was built
`postalCode`	No	ZIP or postal code
`valueCents`	No	What the property itself is worth, in cents (not its contents)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2026.11.10Nov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely non-obvious semantics on top: omitted fields are preserved on update, null explicitly clears a field, and the call returns the property with its id. It does not mention permission requirements or what happens to items already attached to a property, but the merge-vs-null rule is the critical behavioral disclosure for a partially-optional update schema.

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 definition, then add-mode, then change-mode, then the sibling boundary and the return value. No sentence is redundant and the two modes are cleanly separated by 'To add:' / 'To change:'.

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

Completeness5/5

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

For an 11-parameter upsert with no output schema, the definition covers the mode switch, the only required field, defaults, merge semantics, sibling boundaries, and the return value. Combined with annotations and full schema descriptions, an agent has everything needed to call it correctly.

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%, so the baseline is 3, and the description earns above that by adding two facts not in the schema: type defaults to home when omitted, and an omitted field is preserved while null clears it. The field list ('rename, kind, address, year built, value, notes') is a loose paraphrase of the parameter names and even says 'value' where the schema says valueCents, which is a minor mismatch but recoverable.

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?

Opens with a specific verb and resource ('Adds a property') and immediately defines the resource ('a home, vacation home, rental, storage unit or vehicle, the top level of where things are kept'). It then splits the tool's two modes and names the sibling it is not ('Rooms, closets and shelves inside it are save_location'), so an agent can place it correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing for both modes: add requires only name (type defaults to home) and should be preceded by list_locations to avoid duplicates; change requires id and is the path for renames/address/year/value edits. It also names the boundary alternative, save_location, for sub-units. That is when/when-not plus alternatives in three sentences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.