Skip to main content
Glama

Odoo

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world. Description adds value: derives from CF analytics-engine, no PII, caching 5min-1h. No contradiction.

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 plus bullet-point use cases. Front-loaded with core functionality. Every sentence adds information; no fluff.

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?

Single optional param, no output schema needed. Description fully covers what it returns, use cases, data source, caching, and privacy. No gaps.

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 100% with enum and description. Description adds explanatory context on window choice (hot vs steady-state), enhancing beyond schema.

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?

Clearly states it returns top tools, packs, and call volume over a window, with three explicit use cases that differentiate it from sibling tools like ask_pipeworx or deep_research.

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?

Lists specific scenarios for use (discovering hot data, confirming canonical tools, aligning use case). Lacks explicit 'when not to use' but context is clear.

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