Skip to main content
Glama
Sign In

MCP for Claude & ChatGPT

by com.tuqui
OverviewDiscussionsAdmin

Delete records

odoo_unlink
Destructive

Delete one or more Odoo records — IRREVERSIBLE, so it takes two turns. The model must be on the workspace's write whitelist with can_unlink=true. The first call returns a preview (display_name + id of each record) and deletes nothing: show that list to the user and end your turn. confirm=true only deletes once the USER has replied after seeing the preview — you cannot confirm your own delete in the same turn. Hard limit of 50 ids per call.

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>",
      "ids": "<ids>"
    },
    "name": "odoo_unlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRecord IDs to delete (max 50).
modelYesOdoo model technical name.
confirmNoSet to true ONLY after the user replied confirming a preview you already showed them. Setting it in the same turn as the preview returns the preview again.
consent_tokenNoThe approval a person gave for THIS call in Tuqui. Bound to these arguments and valid once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, yet the description goes well beyond them: it declares irreversibility, a mandatory two-turn preview gate, an authorization requirement, and a 50-id hard limit. It even describes what the first call returns (display_name + id) and that it deletes nothing.

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 the destructive verb and the IRREVERSIBLE warning, then the procedural constraints in the order an agent needs them. The closing 'Hard limit of 50 ids per call' partly duplicates maxItems in the schema, a small redundancy in an otherwise dense, waste-free description.

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 destructive mutation with no output schema, the description covers authorization, the two-turn confirmation flow, what the preview returns, and the batch limit — everything needed to call it correctly and safely. Only the return shape of the final confirming call is unstated, which is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics for confirm — that setting it in the same turn merely re-returns the preview — and reinforces the 50-id ceiling on ids. consent_token is left to its schema text.

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?

Opens with a specific verb and resource ('Delete one or more Odoo records') and immediately separates itself from the write/create siblings by being the destruction tool. It also names the scope (model + ids) and the two-turn protocol, so an agent can identify it without opening the schema.

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?

Gives explicit invocation guidance: confirm=true only after the user has replied to a preview, and never in the same turn as the preview. It also states the prerequisite (workspace write whitelist with can_unlink=true). It does not name an alternative sibling (e.g. odoo_write) for non-destructive edits, so it stops short of full routing guidance.

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