Skip to main content
Glama
Sign In
Ferret

Ferret

by ferret-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Move an item

move_item
Idempotent

Records an item's new location so its history reflects where it is now; moving a box moves its contents, and null means nowhere.

Instructions

Records that an item now lives somewhere else: a location from list_locations, or null for nowhere in particular. Use it for "I put the drill in the basement"; moving a box takes what's inside it along, and moving something that was in a box takes it out of the box. To put something into a box, use update_item with containerItemId. The move shows in item_history.

Input Schema

NameRequiredDescriptionDefault
idYesThe item's id, from search_inventory
locationIdYesWhere it is now, from list_locations; null: nowhere in particular

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"The item's id, from search_inventory"
    • addedInput schema / properties / locationId / description
      Added value: +"Where it is now, from list_locations; null: nowhere in particular"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, idempotent, non-destructive write; the description adds the cascade semantics that matter operationally: moving a box carries its contents, moving a contained item removes it from that box, and the change is logged in item_history. Those side effects are absent from the annotations and schema.

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 core action and then the containment exception; the conversational example earns its place because it disambiguates the containment edge case. Slightly loose phrasing ("nowhere in particular" repeated) but no wasted bulk.

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 two-parameter mutation with no output schema, the description covers cascade behavior, the box alternative, and the audit trail. It does not say what happens on an invalid or deleted locationId, which is the main residual gap.

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 coverage is 100% and both parameters already document their source tools (search_inventory, list_locations) and the null meaning. The description restates the same locationId semantics nearly verbatim, adding little beyond the schema.

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+resource: it records that an item now lives at a new location, and explicitly contrasts with put-something-into-a-box (update_item). An agent can distinguish it from update_item and adjust_stock 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 a concrete colloquial trigger ("I put the drill in the basement") and names the sibling plus its parameter to use instead when the intent is containment. When-to-use and when-to-use-something-else are both explicit.

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