remus-mcp

Overview Schema Source Related Servers Discussions Admin

export_xml

Export project data from REMUS Jet databases as XML. Apply optional document and ID filters to control exactly which records are included.

Instructions

Export 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": {
      "project_id": "<project_id>"
    },
    "name": "export_xml"
  }
}

Input Schema

Name	Required	Description	Default
`document`	No
`filter_ids`	No
`project_id`	Yes
`filter_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

D1.3/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not indicate whether the operation is read-only, whether it triggers any side effects, or what happens to the data. For an export tool, one might expect a read-only hint, but nothing is stated. This is a significant gap.

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 description is extremely concise (two words) but is under-specified rather than concise. It lacks any structure or front-loading of important constraints. While brevity is positive, it comes at the cost of essential information, making this ineffective.

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

Completeness1/5

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

Given the tool has 4 parameters, no output schema, no annotations, and a vague description, the description is completely inadequate. An agent would be unable to call this tool correctly without external knowledge. It needs to specify what is exported, how parameters interact, and what the output format is.

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 description coverage is 0%, and the description does not compensate. It does not explain the meaning of project_id, filter_ids, filter_type, or document. An agent has no idea what these parameters do or how they affect the export. The description adds no value beyond the bare parameter names in the 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 'Export XML' essentially repeats the tool name without adding any specificity. It does not state what data is exported, for which resource, or what 'XML' refers to. The presence of a project_id parameter suggests exporting a project's XML, but this is not mentioned. This is a vague purpose with no differentiation from siblings like import_xml.

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 use this tool versus alternatives, nor any mention of prerequisites or context. It does not note that this complements import_xml or that it might be used for exporting project data in XML format. The description provides zero usage context.

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