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

live-mcp-for-1c

by vlikhobabin

execute_1c_query

Executes admitted read-only 1C queries via AIDataRead and returns JSON or CSV results for reporting and data inspection.

Instructions

Execute an admitted read-only 1C query through AIDataRead.

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": "execute_1c_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitsNo
parametersNo
query_textYesAdmitted read-only 1C query text to execute.
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?

No annotations are supplied, so the description carries the full burden. It does assert the operation is read-only, which is useful safety context, but it says nothing about behavior on rejected/unadmitted queries, execution limits or truncation, rate limiting, or what the 'limits' object controls. For a query-execution tool that passes caller-supplied limits and parameter arrays, this leaves key runtime behavior undisclosed.

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?

The single sentence is front-loaded with the verb and free of redundancy, which is good structure. However, brevity here amounts to under-specification rather than conciseness: the same short sentence would need to carry far more information given six parameters and a nested object.

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?

With six parameters, a nested 'limits' object, no annotations, and no output schema, this is a complex tool. The description gives no return-shape expectations, no error semantics, and no prerequisite workflow, so an agent cannot call it confidently without reverse-engineering the schema and sibling tools.

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 50%. The description adds no meaning beyond the schema for the undocumented parameters: 'limits' (a nested object with an empty default) and 'parameters' (an array of up to 64 objects) are entirely unexplained, and the description does not clarify the expected query dialect or parameter binding format. Only the required query_text is self-evident from the name.

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 verb 'Execute' plus the resource '1C query' gives a concrete action, and 'read-only' narrows the intent. But the qualifier 'admitted' is unexplained jargon and 'AIDataRead' is opaque, so an agent cannot tell what an 'admitted' query is or how it relates to 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?

There is no when-to-use or when-not-to-use guidance. The description never states that a query must be validated first (via the sibling validate_1c_query), nor when to prefer execute_dcs_schema or render_dcs_schema instead. The only hint is the adjective 'admitted', which the agent must guess at.

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