Skip to main content
Glama
ilyautov

sbis-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sbis_call_method

Read-only

Retrieve data from SBIS API by calling read-only endpoints using operation ID. Returns JSON with status and data, no changes made.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://saby.ru/help/integration/api.

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

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

Beyond the readOnlyHint annotation, it discloses that reads run without confirmation, that the response is a JSON envelope or error envelope, and that some read endpoints accept a body. These details help the agent predict runtime behavior and error handling.

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 compact, front-loaded with purpose, and each sentence earns its place: purpose, target API, read-only confirmation note, sibling routing, parameter summary, and return shape. No wasted words.

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 read-only catalog call tool with an output schema and helpful annotations, the description covers target API, lookup method for operation_id, parameter semantics, sibling alternatives, and error returns. Nothing needed for correct invocation is missing.

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?

Schema description coverage is 0%, but the description compensates by explaining operation_id as catalog id, path_values as placeholders, query as query-string parameters, and body as an optional JSON request body. It adds meaning for all four parameters beyond raw schema properties.

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 states a specific action: execute one READ endpoint from the catalog by operation_id, identifying both the resource (catalog endpoints) and the identifier mechanism. It explicitly contrasts itself against write and delete siblings, so an agent can distinguish it from sbis_write_method and sbis_delete_method without opening schemas.

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?

It says exactly when to use this tool: for read-only catalog operations, and explicitly routes write and delete behavior to named siblings. It also directs the agent to sbis_search_methods to find operation_id, which is practical usage guidance.

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