Skip to main content
Glama
odoo-mcp

odoo-mcp

by affifariza04

check_stock

Read-only

Retrieve on-hand product quantities flagged as ok, low, or out, and set only_low=true to generate a reorder list for stock replenishment.

Instructions

On-hand quantity per product, flagged ok / low / out. Use only_low=true for a reorder list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
only_lowNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's job is lighter. The description adds the ok/low/out classification behavior, but omits relevant traits such as whether an empty query returns the full catalog, whether results are paginated or truncated, and how matching works. The output schema exists, so not restating return values is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what the tool returns and followed by the one actionable usage hint; nothing is redundant. The extreme terseness is partly responsible for the uncovered query semantics, but there is no wasted wording.

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?

For a simple two-parameter read-only tool with an output schema, the description covers the core behavior and the main filter. It is not complete enough for the undocumented query parameter and the unstated default behavior when query is omitted, both of which an agent needs to call it correctly.

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 0%, so the description must carry the burden, and it only partly does: only_low is explained functionally as a reorder-list filter, which is genuinely useful. The query parameter — defaulting to an empty string — is never explained; an agent cannot tell whether it is a product name, SKU, partial match, or free-text search.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and the returned concept clearly: on-hand quantity per product, each flagged ok / low / out. That is far more specific than a restatement of the name, and no sibling tool (quotations, invoices, customers, sales report, record search) overlaps with stock checking. It lacks an explicit verb and does not explicitly distinguish itself from siblings, so it stops short of a 5.

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?

"Use only_low=true for a reorder list" gives one concrete when-to-use cue tied to a parameter. There is no guidance on when not to use it, no discussion of how it relates to search_records or other data-retrieval siblings, and no hint about what an empty query means (list everything vs. nothing).

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