Fetch a 7NOW product's nutrition, ingredients, allergens, size or flavor variants, and related items. Use sevennow_search or sevennow_category to find products.
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Required. 7NOW product id, from GET /7now/search, /7now/catalog or /7now/category. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope context by listing the data dimensions returned, but discloses no auth, rate-limit, or freshness behavior. Adequate against the lowered bar set by annotations.
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?
Two sentences, zero waste. The capability statement is front-loaded and the routing hint follows cleanly, which is exactly the right ordering for an agent scanning for selection signals.
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?
An output schema exists, so return values need no explanation. The single required parameter is fully documented in both the description and schema, and the discovery path to obtain a product_id is stated. Nothing an agent needs to invoke it correctly is missing.
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 100%, so product_id is already fully documented, including its source endpoints (GET /7now/search, /7now/catalog, /7now/category). The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.
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 (Fetch) and resource (a 7NOW product) and enumerates the specific content returned: nutrition, ingredients, allergens, size/flavor variants, and related items. This clearly distinguishes it from the discovery siblings sevennow_search and sevennow_category.
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?
Explicitly routes the agent: 'Use sevennow_search or sevennow_category to find products.' This tells the agent when this tool is NOT the right choice and names the alternatives. It stops short of spelling out the prerequisite (already holding a product_id), so it's strong but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
