erp2pdf-studio-mcp

Overview Schema Source Related Servers Discussions Admin

get_template

Retrieves one template by ID with its full layout and mapping data, enabling agents to inspect or reuse existing Odoo PDF and HTML template definitions.

Instructions

Get one template with its full layout and mapping.

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": {
      "template_id": "<template_id>"
    },
    "name": "get_template"
  }
}

Input Schema

Name	Required	Description	Default
`template_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. "Get" implies a read operation and "full layout and mapping" usefully describes the return composition, but permissions, error behavior, and read-only guarantees are not stated.

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 a single front-loaded sentence with no wasted words. It is appropriately sized for a simple retrieval tool.

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?

For a simple one-parameter read tool, the description covers the core purpose and return contents. However, with no annotations, no output schema, and an undocumented parameter, it leaves gaps around input meaning and failure behavior.

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

Parameters2/5

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

The sole parameter template_id has 0% schema description coverage and is not explained in the description. The description does not clarify the expected identifier format or source, so it adds little beyond the schema.

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

Purpose4/5

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

The description states a specific verb ("Get") and resource ("one template") and adds what is returned ("full layout and mapping"). The singular "one template" distinguishes it from the sibling list_templates, though it does not explicitly name alternatives.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer it is for retrieving a single template, but there is no stated condition for choosing this over list_templates or get_email_template.

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