Yandex Cloud MCP Server

invoke_function

Invoke a Yandex Cloud serverless function by ID and pass an optional JSON payload to trigger its execution.

Instructions

Вызвать serverless-функцию с payload.

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": {
      "function_id": "<function_id>"
    },
    "name": "invoke_function"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	No	JSON payload для вызова функции	{}
`function_id`	Yes	ID serverless-функции

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of explaining behavior. It only says 'invoke with payload' and does not disclose whether invocation is synchronous, whether it creates resources, what errors may occur, or what the operation returns. This is a significant gap for a mutation-like operation.

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

Conciseness4/5

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

The description is a single clear sentence with no filler; it is appropriately sized for a simple tool. It does not earn points for extra guidance, but it is not bloated or redundant.

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?

For a tool with no annotations and no output schema, the description should disclose return behavior, side effects, and invocation semantics. The current text is minimal and leaves the agent without enough context to predict the result of the call or handle failures.

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

Parameters3/5

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

Schema coverage is 100% and both parameters have descriptions, so the baseline is 3. The description mentions payload but adds no meaning beyond what the input schema already provides—no format hints, invocation type, or relationship between function_id and payload.

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 'Вызвать serverless-функцию с payload' gives a specific verb (invoke) and resource (serverless function), plus the key input (payload). It is clearly distinguishable from siblings like list_functions, get_operation, and start_instance/stop_instance.

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?

The description provides no guidance about when to use this tool versus alternatives, and no exclusions or prerequisites. Sibling tool names hint at the difference, but the description itself does not say 'use this instead of list_functions' or similar.

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

Deploy Server