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

live-mcp-for-1c

by vlikhobabin

validate_1c_query

Parses and validates read-only 1C query text without executing it, catching syntax or access errors before any query runs.

Instructions

Parse and admit a read-only 1C query without executing it.

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": {
      "query_text": "<query_text>"
    },
    "name": "validate_1c_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitsNo
parametersNo
query_textYesRead-only 1C query text to parse and admit.
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.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose the two most important traits (read-only, no execution), but leaves open whether "admit" has side effects such as registering/caching the query, what a rejection looks like, and what the call returns in the absence of an output schema.

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?

A single front-loaded sentence with no filler. It is efficient but arguably over-compressed for a five-parameter, nested-object tool, and the ambiguous term "admit" costs a little clarity.

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 five parameters, nested objects, no annotations, and no output schema, one sentence is not enough. An agent cannot learn the shape of a successful admission result or the limits/parameters defaults without opening the schema.

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 60% and the description names none of the five parameters. Two nested parameters ("limits", "parameters") have no schema description at all and get no help from the description, so the gap is unmitigated.

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?

States a specific verb pair ("parse and admit") and resource ("read-only 1C query"), and the clause "without executing it" implicitly contrasts it with execute_1c_query. The only weakness is that "admit" is jargon an agent may not resolve without guessing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "without executing it" implies this is the pre-flight/validation step before execute_1c_query, but the description never states that ordering, nor when not to use it or what to do when validation fails. Usage is inferable but not spelled out.

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