Skip to main content
Glama
Sign In
Odoo Claude MCP

Odoo Claude MCP

by rosenvladimirov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_share

Share personal memory files by copying them to shared storage, enabling colleagues to pull them. Specify a filename or use '*' to share all files.

Instructions

Share personal memory file(s) — copies to shared storage so colleagues can pull. Use filename='*' to share ALL personal files.

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": {
      "filename": "<filename>"
    },
    "name": "memory_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesPersonal file to share, or '*' for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations; description clarifies copy operation and sharing intent but omits details on permissions, overwrite behavior, or retrieval mechanism.

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?

Extremely concise with two front-loaded sentences, no fluff, and every word adds value.

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

Completeness4/5

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

Adequate for a simple single-parameter tool; mentions wildcard and basic action. Could be more complete with reference to retrieval via memory_pull or error handling.

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 already describes the parameter well (100% coverage). Description adds value by demonstrating the '*' wildcard usage, raising the score above baseline of 3.

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 verb (share), resource (personal memory files), and the action (copies to shared storage) with the purpose of making files accessible to colleagues.

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?

Provides specific usage hint with filename='*' to share all files, but lacks explicit when-not-to-use or alternative sibling tools like memory_pull.

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