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

live-mcp-for-1c

by vlikhobabin

execute_dcs_schema

Executes a supported Data Composition Schema to produce a value collection from 1C data, accepting parameters and returning JSON or CSV output.

Instructions

Execute a supported Data Composition Schema into a value collection.

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

Input Schema

NameRequiredDescriptionDefault
limitsNo
parametersNo
schema_xmlYesData Composition Schema XML with schemaVersion 1; at most 1048576 UTF-8 bytes.
output_formatNojson
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.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure and does not meet it: it never says whether execution is side-effect free, what happens on an unsupported or malformed schema, whether there are size or concurrency limits, or what a "value collection" looks like. Only "supported" hints that some inputs will be rejected, without saying how that surfaces.

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

Conciseness3/5

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

It is a single front-loaded sentence with no wasted words, which is structurally clean. The concision comes at the cost of under-specification rather than efficient communication.

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 tool with six parameters, nested objects, no output schema, and no annotations, one sentence is far short of what an agent needs. The return shape, error behavior, and the meaning of `limits` and `parameters` are all left unresolved.

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 coverage is 50%: schema_xml, correlation_id, and requested_user are documented, but the nested `limits` object and the 64-item `parameters` array have no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented half, including the nested structure flagged by the schema.

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 names a specific verb and resource ("Execute a supported Data Composition Schema") and gestures at output ("into a value collection"), which separates it loosely from render_dcs_schema and validate_dcs_schema. However, "supported" and "value collection" are undefined, so the agent cannot tell what schemas qualify or what actually comes back.

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 statement of when to use execution versus validation or rendering, no prerequisites (e.g., validate first), and no exclusions. The only usage signal is the adjective "supported", which is never expanded.

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