erp2pdf-studio-mcp

Overview Schema Source Related Servers Discussions Admin

get_sample_record

Preview an Odoo model's record data shape using real connector data when configured or a bundled sample, so you can inspect fields before template work.

Instructions

The record previews are rendered with (real when a connector is configured, else the bundled sample): shows the data shape.

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": {
      "model": "<model>"
    },
    "name": "get_sample_record"
  }
}

Input Schema

Name	Required	Description	Default
`model`	Yes
`record_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 26, 2026

TDQS

D1.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one useful behavioral trait — the data may be real or a bundled sample depending on connector configuration — but says nothing about permissions, failure modes, or the record_id default behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but front-loads the rendering mechanism instead of the action, and the parenthetical about connectors buries the only useful hint (that data may be synthetic).

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?

With no annotations, no output schema, and 0% parameter coverage, the description needed to explain what is returned and what the parameters mean. It covers almost none of that, leaving an agent unable to call the tool confidently.

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 mentions neither the required 'model' parameter nor the optional 'record_id'. Nothing compensates for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description talks about how 'record previews are rendered' rather than stating that the tool retrieves a sample record for a given model. The purpose is only inferable from the name, and no sibling (search_records, get_values) is differentiated.

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

Usage Guidelines1/5

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

There is no guidance on when to call this tool, when to use search_records or get_values instead, or any prerequisite such as a valid model. The agent is left to guess from the name alone.

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