Skip to main content
Glama
erpipe-org

Odoo MCP Server

by erpipe-org

read_attachment

Read-onlyIdempotent

Retrieve Odoo attachment metadata and base64 content by attachment ID, with size-capped data for efficient transfer.

Instructions

Read an ir.attachment's metadata and size-capped base64 content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNo
include_dataNo
attachment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoReporting tool name.
errorNoSanitized error message when success is false.
successYesFalse when the call failed; see error.
warningsNo
max_bytesNo
attachmentNoir.attachment metadata row.
data_base64NoBase64 content when under the size cap.
data_includedNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv1.1.0
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / properties / attachment
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "ir.attachment metadata row.",
      +  "title": "Attachment"
      +}
    • addedOutput schema / properties / data_base64
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Base64 content when under the size cap.",
      +  "title": "Data Base64"
      +}
    • addedOutput schema / properties / data_included
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Data Included"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Sanitized error message when success is false.",
      +  "title": "Error"
      +}
    • addedOutput schema / properties / max_bytes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Max Bytes"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "title": "Result",
      -  "type": "object"
      -}
    • addedOutput schema / properties / success
      Added value: +{
      +  "description": "False when the call failed; see error.",
      +  "title": "Success",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / tool
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Reporting tool name.",
      +  "title": "Tool"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Warnings"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "success"
      +]
    • changedOutput schema / title
      Previous value: -"read_attachmentOutput"New value: +"ReadAttachmentResponse"
  2. Addedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the behavioral trait of 'size-capped base64 content', warning about potential truncation. This adds value beyond annotations, but only marginally.

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?

The description is a single concise sentence with no wasted words. However, it omits necessary parameter details, so it sacrifices completeness for brevity.

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

Completeness2/5

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

Given the tool has 3 parameters (one unexplained), the description is incomplete. It does not explain the optional parameters 'instance' and 'include_data'. Although an output schema exists, the missing parameter documentation is a significant gap.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain any parameter semantics. It does not clarify the meaning of 'instance' or 'include_data'. Only 'attachment_id' is inferable from context.

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 verb 'Read', the resource 'ir.attachment', and specifies what is read: 'metadata and size-capped base64 content'. This distinguishes it from sibling tools like 'read_record' or 'search_records'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives. There is no mention of prerequisites or when-not-to-use. The purpose is clear but usage context is not provided.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erpipe-org/mcp-odoo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server