Skip to main content
Glama
Sign In
Yandex Cloud MCP Server

Yandex Cloud MCP Server

by romati88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_disk_details

Retrieve detailed configuration of a Yandex Cloud disk by ID, covering size, type, status, and more. Ideal for verifying disk settings and auditing infrastructure.

Instructions

Get detailed disk configuration

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": {
      "disk_id": "<disk_id>"
    },
    "name": "get_disk_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
disk_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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. It implies a read-only operation but does not disclose any specific behavioral traits like required permissions, possible errors, or what 'detailed' configuration includes.

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 concise sentence with no filler, and it front-loads the core purpose. However, it is terse to the point of under-specification, lacking any structural elaboration.

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 simple getter with one parameter and no output schema, the description is minimally adequate but leaves significant gaps: it does not mention the relationship to list_storage_disks, what 'detailed configuration' entails, or what the return value looks like.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no meaning to the disk_id parameter. It does not explain what disk_id refers to or how to obtain it, leaving the agent without essential invocation information.

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

Purpose4/5

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

The description states a specific verb ('Get') and resource ('detailed disk configuration'), clearly indicating it retrieves details about a disk. It is distinct from sibling tools like list_storage_disks, though it does not explicitly differentiate from get_disk_type_configuration.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or typical usage context. The agent must infer from the name and siblings.

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