Skip to main content
Glama
Sign In
Ferret

Ferret

by ferret-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add a location

create_location

Adds a room, closet, or shelf to a property, optionally nested under a parent location or created with child locations in one call. Use it to build out storage hierarchy before assigning items.

Instructions

Adds a location — a room, closet or shelf — to a property, optionally inside another location (parentId), and optionally with locations inside it in one go: "a garage with three shelves" is name "Garage", children ["Shelf 1", "Shelf 2", "Shelf 3"]. Check list_locations first so you don't add one twice. propertyId can be left out when there's only one property; a new property itself is create_property. Returns the new locations with their ids.

Input Schema

NameRequiredDescriptionDefault
iconNoAn icon name for the app (optional)
nameYesWhat the household calls it: "Garage", "Hall closet", "Top shelf"
notesNoAnything else worth keeping about it
childrenNoNames of locations to make inside it in one go: ["Shelf 1", "Shelf 2"]
parentIdNoThe location it's inside (a shelf in a closet), from list_locations; null: directly in the property
propertyIdNoThe property, from list_locations; can be left out when there's only one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / children / description
      Added value: +"Names of locations to make inside it in one go: [\"Shelf 1\", \"Shelf 2\"]"
    • addedInput schema / properties / icon / description
      Added value: +"An icon name for the app (optional)"
    • addedInput schema / properties / name / description
      Added value: +"What the household calls it: \"Garage\", \"Hall closet\", \"Top shelf\""
    • addedInput schema / properties / notes / description
      Added value: +"Anything else worth keeping about it"
    • addedInput schema / properties / parentId / description
      Added value: +"The location it's inside (a shelf in a closet), from list_locations; null: directly in the property"
    • addedInput schema / properties / propertyId / description
      Added value: +"The property, from list_locations; can be left out when there's only one"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered; the description adds the batch semantics of creating a parent plus children in one call, the propertyId fallback when only one property exists, and the return value (new locations with their ids). It does not mention failure modes, partial-success behavior for batched children, or name-collision handling beyond the list_locations check.

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?

Front-loaded with the action and the definition of what a location is, then prerequisites, then return value — a sensible order. It is dense and slightly run-on with stacked clauses, but no sentence is filler.

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 a 6-parameter creation tool with no output schema, the description covers the duplicate-prevention workflow, the property scoping fallback, the batch-children case, the sibling tool split, and what is returned. Nothing an agent needs in order to call this correctly is missing.

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 baseline is 3; the description earns an extra point by showing how name and children compose in a single call ("a garage with three shelves") and by restating the parentId nesting intent with a concrete room/shelf analogy. Those composite examples add meaning the per-field schema strings do not convey.

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 ("Adds a location") and immediately narrows scope to rooms/closets/shelves belonging to a property. It distinguishes itself from create_property ("a new property itself is create_property") and list_locations, so an agent can pick it out of a crowded sibling list without opening the 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 pre-call guidance ("Check list_locations first so you don't add one twice") and an explicit exclusion pointing at the sibling tool for the adjacent task (create_property). It also resolves the common ambiguity of when propertyId is required.

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

Deploy Server

Other Tools