remus-mcp

by christianmz565

Overview Schema Source Related Servers Discussions Admin

Hybrid

render_html

Render REMUS Jet project documents as HTML or PDF, enabling reports for requirements, defects, and change requests.

Instructions

Render HTML/PDF via Wine msxml3

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>",
      "document": "<document>"
    },
    "name": "render_html"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No
`output`	No
`document`	Yes
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations, the description is the sole source of behavioral context. It only provides an implementation detail ('via Wine msxml3') and does not disclose side effects, permissions, idempotency, output behavior, or whether the operation is read-only or mutates state. This is a significant gap for a tool that likely performs a conversion action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short sentence with no unnecessary filler. It front-loads the core action and output formats, though the 'via Wine msxml3' detail may be less essential. It is concise, but at the cost of missing critical information.

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

Completeness2/5

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

Given 4 parameters, 3 with enums, no annotations, and no output schema, the description is grossly under-specified. It does not explain required inputs, the role of each parameter, expected outputs, or any preconditions. An agent cannot reliably invoke this tool correctly based on the provided definition.

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 for explaining parameters. It does not mention any parameter, its purpose, or constraints. The enums in the schema are self-explanatory to some extent, but the description adds no meaning to 'project_id' or 'document', which remain opaque.

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

Purpose3/5

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

The description states a specific verb, 'Render', with a resource, 'HTML/PDF', indicating the tool produces output in these formats. However, it does not clearly specify what is being rendered (a document, a template, etc.) or how this distinguishes it from siblings like export_xml. The meaning of 'Render' is vague in this context, leaving the purpose partially implied.

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?

No guidance is given about when to use this tool versus alternatives. There is no mention of sibling tools, conditions, or exclusions, leaving the agent without context for selecting this tool over others.

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