Skip to main content
Glama
Sign In

MCP for Claude & ChatGPT

by com.tuqui
OverviewDiscussionsAdmin

Link to a record

odoo_get_record_url
Read-only

Return the portal URL (shareable with customers, no Odoo login needed) and the backend URL (for internal users) for an Odoo record. Common use cases: 'share the invoice with the customer', 'give me a link to this sale order', 'send the delivery tracking URL'. Pass model (e.g. 'sale.order', 'account.move', 'stock.picking') and id. Not all models expose a public portal URL — the tool reports when none is available and always provides the backend URL for internal users.

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": {
      "model": "<model>",
      "id": "<id>"
    },
    "name": "odoo_get_record_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord ID.
modelYesOdoo model technical name (e.g. 'sale.order', 'account.move', 'res.partner').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only/non-destructive; the description adds genuinely useful behavior: the portal URL is customer-shareable without an Odoo login, the backend URL is for internal users, and not all models expose a portal URL so the tool reports when none exists. Since there is no output schema, this disclosure of return shape and edge-case handling carries real weight.

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?

Front-loaded with what is returned and the distinction between portal and backend URLs, followed by use cases and the model caveat. The quoted use cases are slightly verbose but each reinforces a distinct trigger scenario, so little is wasted.

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?

For a two-parameter read-only tool with no output schema, the description fully covers what comes back (two URL types with differing audiences) and the important failure mode (no portal URL available). Nothing an agent needs to call and interpret the result is missing.

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%, so both parameters are already documented with types and model-name examples. The description restates 'pass model and id' and adds a few model examples ('sale.order', 'account.move', 'stock.picking') that largely overlap with the schema's own examples, so it adds little beyond the schema baseline.

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?

The description states a specific action (return portal and backend URLs) applied to a specific resource (an Odoo record), and explicitly characterizes the two return variants. It is immediately distinguishable from sibling read/search tools like odoo_search_read or odoo_read_group, which return record data rather than links.

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

Usage Guidelines4/5

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

Concrete use cases ('share the invoice with the customer', 'give me a link to this sale order') make the triggering intent unmistakable. It does not name a sibling alternative or state when-not to use it, but the usage context is clear enough that no agent would confuse it with a data-retrieval tool.

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

All MCP for Claude & ChatGPT 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