Skip to main content
Glama
Sign In

Odoo MCP Connector for ChatGPT and Claude

by com.speaktoyourdatabase
OverviewDiscussionsAdmin

Get an answer

get_answer
Read-onlyIdempotent

Use this only when ask_question returned status "running": it fetches that answer by its run_id, waiting up to about 20 s. Returns the final answer when it is ready, or status "running" again: then call it again with the same run_id. Uses no prompt of its own (the question's prompt is counted once).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "get_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id that ask_question returned with status "running".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / run_id / description
      Added value: +"The run_id that ask_question returned with status \"running\"."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds the blocking behavior ('waiting up to about 20 s'), the two possible outcomes (final answer vs. status running), and the cost model ('uses no prompt of its own'). These are exactly the traits an agent needs to decide whether to poll.

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

Conciseness5/5

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

One dense sentence whose first clause is the gating condition, followed by outcome and retry semantics. No filler, nothing out of order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description covers the return values (final answer or running status) and the timeout horizon, which is everything an agent needs for this single-parameter polling tool.

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 coverage is 100% and the single run_id parameter is already documented in the schema with the same 'returned with status running' phrasing. The description reinforces that the same run_id is reused across retries, but adds little meaning beyond the structured field, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('fetches that answer by its run_id') and explicitly ties itself to the precondition set up by the ask_question sibling, so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule ('only when ask_question returned status "running"'), names the alternative that precedes it, and even specifies the retry loop: call again with the same run_id if status is still running. Nothing is left to inference.

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

All Odoo MCP Connector for ChatGPT and Claude toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources