Skip to main content
Glama
Sign In
remus-mcp

remus-mcp

by christianmz565
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

import_xml

Import XML data into a REMUS Jet project using a merge or replace strategy. Supports dry-run validation, file path or inline XML, and configurable handling of missing references.

Instructions

Import 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": "import_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlNo
dry_runNo
strategyNo
file_pathNo
project_idYes
on_missing_refNo
confirm_replaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/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 provides none: no mention that this mutates project data, that dry_run can preview changes, that strategy can merge or replace, or that confirm_replace gates destructive 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?

Two words is under-specification, not conciseness. While there is no wasted text, the description is too sparse to be structurally informative or front-loaded with useful content.

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?

This is a 7-parameter tool with an enum, multiple booleans, and no output schema or annotations. The one-line description is wholly inadequate for an agent to call it correctly, understand side effects, or interpret results.

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%, so the description must compensate by explaining parameters. It does not mention xml, file_path, strategy, dry_run, confirm_replace, or on_missing_ref at all, leaving the agent to guess which parameters are required and how they interact.

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 'Import XML' is essentially a restatement of the tool name. It identifies the general action but does not state the target resource, the destination project, or how it relates to sibling tools like export_xml or validate_project.

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?

There is no guidance about when to use this tool over alternatives. The description does not mention validation workflows, export round-trips, or any context where import_xml is preferred or disallowed.

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