Skip to main content
Glama
Sign In
erp2pdf-studio-mcp

erp2pdf-studio-mcp

by c4pointer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_parts

Retrieve shared header and footer parts for Odoo PDF/email templates, optionally filtered by kind, so layouts can reference them by ID.

Instructions

List the shared header/footer parts (templates use them through layout.master_refs = {header: id, footer: id}).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

As there are no annotations, the description is responsible for behavioral context. It discloses key behavioral information by explaining the internal mechanism of how these parts are referenced in templates (`layout.master_refs`), which is important context for the resource.

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, concise sentence that efficiently delivers both the function and the necessary domain context, with no unnecessary filler.

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?

Given the tool's simplicity, the description is reasonably complete. It defines the scope of the parts being listed and provides the necessary internal syntax context for the agent to understand the resource's role.

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?

Since the schema coverage is 0%, the description must carry the burden. It defines the nature of the resource being queried (shared header/footer parts) and contextualizes the `kind` parameter by showing how it relates to template structures.

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 clearly states the action (List) and the resource (shared header/footer parts). It provides enough specific context to distinguish this from general listing functions within the large set of sibling tools.

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 offers no guidance on when to use this tool versus other listing or retrieval tools. There is no 'when/when-not' comparison provided.

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