moysklad-mcp-ru

Overview Schema Source Related Servers Discussions Admin

ms_call_method

Read-only

Execute a read-only operation from the Moysklad API catalog using its operation ID. Retrieve data such as inventory, products, orders, or reports without altering anything.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://dev.moysklad.ru/doc/api/remap/1.2/.

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

Args: operation_id: id from the catalog (see ms_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

Name	Required	Description	Default
`body`	No
`query`	No
`path_values`	No
`operation_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Sep 15, 2026

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

First observedv0.1.0Jul 4, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true, and the description reinforces that by stating 'Reads only: nothing here changes data'. It adds value beyond annotations by disclosing that it 'runs without confirmation' and by describing the success/error envelope ('Returns JSON: {"ok": true, "status", "data"} or the error envelope'). It does not cover rate limits or auth, but the core behavioral traits are well disclosed.

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?

Every sentence earns its place: the purpose is front-loaded, safety implications are stated early, alternatives are named, arguments are summarized compactly, and the return shape is included. The structure is logical and scannable without 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?

For a generic execution tool with four free-form parameters and an output schema present, the description is functionally complete. It provides the target API base URL, tells where to get operation_id, explains each parameter, names sibling tools for other operation types, and gives the response envelope. Nothing essential is missing for an agent to invoke it correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: each parameter gets a practical explanation (operation_id as catalog id, path_values for placeholders, query string parameters, and body for read endpoints that require one). This adds real meaning beyond the bare anyOf objects in the schema, though it stops short of giving syntax examples or formatting details.

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 opens with a specific verb and resource: 'Execute one READ endpoint from the catalog by operation_id', which is immediately clear. It also distinguishes itself from siblings by explicitly framing the tool as read-only and naming write/delete alternatives.

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?

Usage context is explicit: it is for reading data only and runs without confirmation, with clear redirection to ms_write_method for changes and ms_delete_method for deletions. The description also tells the agent where to find valid operation_ids (ms_search_methods), leaving little to inference.

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