Skip to main content
Glama
Sign In
odt-mcp-server

odt-mcp-server

by PeterHeick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

extract_odt_xml

Extracts raw XML content from specified files within an ODT archive, such as content.xml, styles.xml, or meta.xml, for document analysis.

Instructions

Udtrækker rå XML fra en specifik fil i .odt arkivet (content.xml, styles.xml, meta.xml)

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": {
      "file_path": "<file_path>",
      "xml_file": "<xml_file>"
    },
    "name": "extract_odt_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xml_fileYesNavn på XML fil (f.eks. 'content.xml', 'styles.xml', 'meta.xml')
file_pathYesSti til .odt filen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden, yet only states the basic action. No details on side effects, permissions, or error conditions.

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 front-loads the action and context. No redundant or missing words.

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 2-parameter tool with no output schema, the description adequately conveys the core function. However, it omits details about return format, error handling, or performance considerations.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains both parameters. The description adds example values (content.xml, styles.xml, meta.xml) but does not significantly enhance understanding beyond the schema.

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 'udtrækker' (extracts) and the resource 'rå XML fra en specifik fil i .odt arkivet', distinguishing it from siblings like get_odt_metadata and list_odt_files.

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

Usage Guidelines3/5

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

The description implies usage for extracting raw XML from specific ODT archive files, but lacks explicit when-to-use or when-not-to-use guidance and does not mention alternatives.

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