Skip to main content
Glama
ilyautov

diadoc-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

diadoc_call_method

Read-only

Execute a read-only Diadoc API operation by its catalog ID to retrieve document exchange data, status, or other information without altering any records.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://developer.kontur.ru/doc/diadoc-api.

Reads only: nothing here changes data, so it runs without confirmation. To change data use diadoc_write_method, to delete use diadoc_delete_method.

Args: operation_id: id from the catalog (see diadoc_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
queryNo
path_valuesNo
operation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / confirm_write
      Removed value: -{
-  "default": false,
-  "title": "Confirm Write",
-  "type": "boolean"
-}
    • removedInput schema / properties / i_understand_this_modifies_data
      Removed value: -{
-  "default": false,
-  "title": "I Understand This Modifies Data",
-  "type": "boolean"
-}
  2. First observedv0.2.0

TDQS

A5/5.0
Behavior5/5

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

The description adds behavioral details beyond the annotations: it states that reads run without confirmation, and it specifies the return envelope ('{"ok": true, "status", "data"} or the error envelope'). It also explains how path_values, query, and body are used. These are meaningful behavioral traits not present in the annotations or schema.

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

Conciseness5/5

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

The description is well-structured: it opens with the core purpose, then the target API, then the read-only nature, then sibling routing, and finally a concise parameter breakdown. Every sentence adds value, and the most important info (read-only, usage) is front-loaded. No filler.

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

Completeness5/5

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

Given the tool's generic nature (executing arbitrary read endpoints), the description covers all needed context: the API reference URL, the read-only guarantee, how to find operation_id, and the return format. The output schema exists, so the description doesn't need to list return fields. It is complete for an agent to call correctly.

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

Parameters5/5

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

The input schema has zero description coverage, but the description's 'Args' section explains each parameter: operation_id is the catalog id, path_values are for {placeholders} in the path, query is for query-string parameters, and body is a JSON request body for some read endpoints. This fully compensates for the schema's lack of semantic detail.

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

Purpose5/5

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

The description clearly states the action: 'Execute one READ endpoint from the catalog by operation_id.' It specifies a concrete verb, resource (READ endpoint), and the key identifier. It also differentiates from sibling tools by naming diadoc_write_method and diadoc_delete_method for non-read operations, so an agent can distinguish it immediately.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: for read-only operations that run without confirmation. It also names alternatives for changing data (diadoc_write_method) and deleting (diadoc_delete_method), and directs the agent to diadoc_search_methods to find operation_id. This gives clear usage context and exclusions.

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

Deploy Server

Other Tools