grocy-mcp

Location Create Tool

location_create_tool

Create a new storage location to organize household inventory. Provide a name, indicate if it's a freezer, and add an optional description to define where items are kept.

Instructions

Create a new storage location.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Location name (e.g. "Pantry", "Garage fridge").
`is_freezer`	No	Whether this location is a freezer (default false).
`description`	No	Optional description.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description says 'Create' implies mutation/persistence, which is useful, but it does not disclose duplicate-name handling, idempotency, permissions, or any side effects beyond creation.

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?

The description is a single focused sentence with no filler. It front-loads the key action and resource, making it immediately readable.

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

Completeness3/5

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

The parameter schema is complete and an output schema exists, so basic invocation is supported. However, with no annotations, the description lacks behavioral details such as duplicate handling or uniqueness constraints, which would make it more contextually complete.

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% and includes examples and defaults, so the schema already documents all three parameters. The tool description adds no extra parameter meaning 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?

The description clearly states the verb 'Create a storage location' and names the resource type, 'a new storage location', distinguishing it immediately from list/read, update, delete, and generic entity tools. An agent can correctly recognize this as the location-creation operation.

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?

The usage context is implied: use this when a new storage location must be created. It does not mention when not to use it, any prerequisites, or name alternatives like entity_create_tool or locations_list_tool.

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

Deploy Server