commerce_store_createCreate a new Drupal commerce store by supplying a store ID, label, and email address, with optional currency and physical address settings.
Create a new commerce store.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| Yes | |||
| label | Yes | ||
| address | No | ||
| default_currency | No | USD |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. 'Create' implies a write operation, but the description reveals nothing about permissions required, id uniqueness, side effects, or what fields are returned or modified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is front-loaded and has no waste, but it is severely under-specified for a 5-parameter mutation tool. Conciseness here reflects missing content rather than efficient density.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema exists, so return values need not be explained, but with no annotations, 0% schema description coverage, and 5 parameters, the description is far too thin to call the tool correctly. It omits required inputs, constraints, and basic behavioral context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning for any of the 5 parameters. It does not mention required fields (id, label, mail), default_currency, or address.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Create') and resource ('commerce store'), and the verb distinguishes it from sibling tools commerce_store_list, commerce_store_get, and commerce_store_update. An agent can identify the operation 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no when-to-use guidance, prerequisites, or alternatives. It does not say when to create a store versus updating an existing one, nor what happens if the id already exists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.