get_productLiefert die Einzelheiten zu einem Produkt: Beschreibung, Preis, Lagerstatus, Kategorien und Bild.
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Die id aus search_products. |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | product_id fuer create_order | |
| url | No | ||
| name | Yes | ||
| image | No | ||
| price | Yes | ||
| currency | Yes | ||
| in_stock | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It clarifies that the tool returns product details, but it does not explicitly state read-only behavior, error cases, or auth requirements; the verb 'Liefert' only weakly implies a non-mutating read.
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 description is a single sentence that front-loads the action and resource, then lists the returned fields compactly. There is no filler or redundancy.
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?
For a one-parameter read tool with an output schema, the definition is essentially complete: the description lists what is returned, and the schema explains how to obtain the product_id. The reference to search_products in the schema mitigates the only potential workflow gap.
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%, and the schema already explains product_id as 'Die id aus search_products', which is meaningful context. The main description adds no additional parameter semantics, 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?
The description uses a specific verb ('Liefert') and resource ('Produkt') and enumerates the returned fields: Beschreibung, Preis, Lagerstatus, Kategorien, Bild. This clearly distinguishes it from siblings like create_order or get_order_status, which target different resources and actions.
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?
The parameter description states that product_id is 'Die id aus search_products', which explicitly ties usage to a prior search_products call. The description itself does not name an alternative or exclusion, but the workflow context is clear.
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.
Each tool targets a distinct resource or stage: products are searched and read, orders are created and checked, payment links are created, and login has separate start and status tools. The two status tools are clearly separated by domain, so an agent is unlikely to confuse them.
All tools use a consistent snake_case verb_noun pattern such as create_order, get_order_status, search_products, and start_login. The action words are specific and the objects are clear, making the expected behavior predictable across the entire set.
Seven tools is well within the ideal range for a focused commerce demo. Each tool covers a necessary step in the demo workflow without redundant additions or unnecessary complexity.
The tool surface covers the full demo workflow: product discovery, order creation, payment-link generation, order status checks, and the external login flow. The demo's explicit constraints make the absence of admin operations such as update or delete acceptable, and there are no dead ends.