Retrieve complete product details from Odoo by specifying the product ID. Use this tool to access product information for inventory management, sales, or purchasing workflows.
Get details of a specific product.
Args:
product_id: Product ID
Returns:
Complete product details
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
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. It states the tool retrieves product details but doesn't cover important aspects like whether it's a read-only operation, authentication requirements, error handling, or rate limits. The description is minimal and lacks behavioral context.
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 highly concise and well-structured, with a clear purpose statement followed by brief sections for arguments and returns. Every sentence serves a purpose without unnecessary elaboration, making it easy to parse quickly.
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?
Given the tool's low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema description coverage, it lacks details on behavioral traits and parameter nuances, leaving gaps in understanding how to use the tool effectively.
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?
The description adds minimal parameter semantics by naming 'product_id' and stating it's for a 'specific product', but schema description coverage is 0%, so the schema provides no additional details. The description doesn't explain the parameter's format, constraints, or examples, offering only basic context beyond the schema.
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 clearly states the tool's purpose with a specific verb ('Get details') and resource ('specific product'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'list_products', which retrieves multiple products rather than a single one.
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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'list_products' for browsing multiple products or clarify prerequisites such as needing a valid product ID. Usage context is implied but not explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/industream/mcp-odoo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server