Skip to main content
Glama

Odoo

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. Description adds behavioral context: memory is scoped by identifier, persistent for authenticated users, 24-hour retention for anonymous sessions. No contradiction with annotations.

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?

Three sentences, no wasted words. Front-loaded with purpose, then usage, then technical details. Every sentence is substantive.

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 simple key-value write tool with no output schema, the description covers purpose, usage, persistence, pairing, and parameter conventions. Fully adequate for an agent to use correctly.

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 coverage is 100%, but description adds value by providing key naming conventions (e.g., 'subject_property', 'target_ticker') and clarifying value is 'any text — findings, addresses, preferences, notes', which goes beyond schema definitions.

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?

Description starts with a clear verb ('Save data') and resource ('data the agent will need to reuse later'). It provides concrete examples of what to store (resolved ticker, target address, user preference) and explicitly pairs with recall and forget, distinguishing it from siblings.

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?

Description explicitly states when to use ('when you discover something worth carrying forward') and pairs with recall/forget for lifecycle management. It does not explicitly state when not to use or provide alternatives, but the context is clear enough.

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

All Odoo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Some tools have overlapping purposes (e.g., ask_pipeworx and ask_pipeworx_grounded; multiple Polymarket analysis tools) but descriptions help differentiate. Odoo-specific tools are distinct among themselves but muddled with many general-purpose tools.

Naming Consistency2/5

Naming is heavily inconsistent: Odoo tools follow 'odoo_list_*' pattern while others use varied structures like verb-first (forget, remember) or noun-first (entity_profile, recent_alerts). No unified verb_noun pattern across the set.

Tool Count3/5

At 32 tools, the server exceeds the typical well-scoped range (3–15) but is not excessively large. Many tools are generic and could be trimmed, making the set feel heavier than necessary.

Completeness2/5

Despite many tools, the server lacks essential CRUD operations for Odoo (e.g., create/update/delete leads) and the 'Odoo' name misrepresents the actual focus. Gaps in Odoo functionality and mixed domains create a sense of incompleteness.

Resources