Skip to main content
Glama
ilyautov

vk-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vk_call_method

Read-only

Executes a read-only VK API method from the catalog by operation ID, returning data without altering anything. Use for safe queries; for modifications, use write or delete tools.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://dev.vk.com/ru/method.

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

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

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's safety-critical addition is modest but real: 'Reads only: nothing here changes data, so it runs without confirmation.' It also discloses the return shape as a JSON success envelope or error envelope. This adds value beyond the annotations without contradicting them.

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 tightly structured with a front-loaded purpose, a short safety note, explicit sibling routing, and a concise parameter list. Every sentence contributes either to invocation, selection, or behavior — there is no padding.

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 catalog-driven read tool with an output schema already present, this description covers everything needed to invoke it correctly: target API, operation_id source, param usage, read-only behavior, and return shape. It also routes to write/delete alternatives, making the surrounding toolset navigable without further research.

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 carry the semantic weight. It does: operation_id is traced to the catalog, path_values maps to path placeholders, query is identified as query-string parameters, and body is explained as a JSON body used by a few read endpoints. These are generic but correct meanings that the raw schema does not provide.

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 clear verb and resource: 'Execute one READ endpoint from the catalog by operation_id.' It explicitly contrasts itself with vk_write_method and vk_delete_method, making the tool's scope and read-only purpose unambiguous even before looking at the schema.

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 explicitly states when to use this tool: for read-only catalog endpoints, and it names concrete alternatives for mutation and deletion ('To change data use vk_write_method, to delete use vk_delete_method'). It also tells the agent where to get operation_id from ('see vk_search_methods'), removing ambiguity about prerequisites.

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