Skip to main content
Glama
live-mcp-for-1c

live-mcp-for-1c

by vlikhobabin

render_dcs_schema

Render a supported Data Composition Schema from XML and optionally persist the rendered output as an XLSX file.

Instructions

Render a supported Data Composition Schema and optionally persist XLSX.

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": {
      "report_id": "<report_id>",
      "schema_xml": "<schema_xml>"
    },
    "name": "render_dcs_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitsNo
outputNo
report_idYesReport identifier used by the service for the artifact name.
parametersNo
schema_xmlYesData Composition Schema XML with schemaVersion 1; at most 1048576 UTF-8 bytes.
correlation_idNoOptional correlation id echoed by the service.
requested_userNoOptional diagnostic user hint; never impersonation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions optional XLSX persistence, which signals a possible side effect, but does not explain what rendering means, where artifacts are persisted, whether the operation is read-only, or what permissions or limits apply.

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 front-loaded sentence with no unnecessary wording. It is concise, though its brevity contributes to gaps addressed in other dimensions rather than being a structural flaw here.

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?

For a seven-parameter tool with nested objects, no annotations, and no output schema, the description is too thin. It omits key context about supported schemas, rendering behavior, artifact persistence, error conditions, and the roles of the undocumented parameters.

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

Parameters2/5

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

Schema description coverage is only 57%, and the description adds essentially no meaning for the seven parameters. It does not clarify limits, output, parameters, or how optional XLSX persistence maps to the output parameter.

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 states a specific verb and resource: render a Data Composition Schema, with optional XLSX persistence. It is clear enough to distinguish this from a generic execution tool, but it does not explicitly contrast with siblings such as execute_dcs_schema or validate_1c_query.

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 gives no guidance on when to use this tool versus execute_dcs_schema, validate_1c_query, or execute_1c_query. It also does not state prerequisites, supported-schema constraints, or when the XLSX persistence option should be used.

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