Skip to main content
Glama
Sign In
Odoo Claude MCP

Odoo Claude MCP

by rosenvladimirov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

proxy_call

Forward tool calls to internal MCP sub-services: manage Docker/K8s, GitHub repos/issues/PRs, or MS Teams messages. First use proxy_discover to list available tools.

Instructions

Forward a tool call to an internal MCP sub-service. Available services: 'portainer' (Docker/K8s management, 38 tools), 'github' (repos/issues/PRs, 20 tools), 'teams' (MS Teams messaging, 6 tools). Use proxy_discover first to see available tools on each service.

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": {
      "service": "<service>",
      "tool": "<tool>"
    },
    "name": "proxy_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool name on the target service
serviceYesTarget MCP service
argumentsNoTool arguments (as JSON object)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must bear the full burden. It discloses the forwarding action and service details but omits behavioral traits like side effects, authentication requirements, error handling, or whether it is destructive or read-only.

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?

The description is concise, with two sentences front-loading the purpose. Every sentence provides value.

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

Completeness3/5

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

Given the complexity of forwarding calls to sub-services with many tools, the description is adequate but lacks details on argument formatting per service, error responses, or output format. With no output schema, more completeness would be beneficial.

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 the schema already documents each parameter. The description adds minimal extra meaning, only briefly mentioning services (already in enum) and that arguments are a JSON object.

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 clearly states the tool forwards a tool call to an internal MCP sub-service, lists the available services, and provides context on tool counts. It distinguishes itself from siblings like proxy_discover.

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?

The description explicitly advises using proxy_discover first to see available tools, guiding when to use this tool. However, it does not specify when not to use it or mention alternatives beyond proxy_discover.

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

Deploy Server

Other Tools