Skip to main content
Glama
cloud-mcp
by AVert

cloud_search

Read-only

Find API operations across Timeweb Cloud, Selectel, and Tilda by free-form query in Russian or English; returns matching tool names, methods, and parameters.

Instructions

Find API operations across providers by a free-form query (RU or EN); returns the best matches with their tool names, methods and parameters

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": {
      "query": "<query>"
    },
    "name": "cloud_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNodefault 5
kindNoread|write|destructive|paid
queryYes
productNoselectel product slug
providerNotimeweb|selectel|tilda

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description need not restate safety. It adds genuine context beyond that: queries are free-form and accept Russian or English, and results are ranked ('best matches') and include tool name, method and parameters. Missing only pagination/truncation behavior for the 'top' cutoff.

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?

A single front-loaded sentence with no filler; the purpose comes first and the return description follows after the semicolon. Slightly dense but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description usefully compensates by summarizing the result fields, which suits a read-only discovery tool. However, it says nothing about how the optional filters (kind, product, provider) or the implicit 'top' cap should be used, leaving the agent to infer search-narrowing strategy from the schema alone.

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 description coverage is 80%, so most parameters are already documented and the baseline is 3. The description only adds meaning for one of them, clarifying that 'query' is free-form and bilingual (RU or EN); the filtering parameters (kind, product, provider, top) get no additional explanation.

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 names a specific verb and resource ('Find API operations across providers') and adds the mechanism ('by a free-form query') plus the return shape ('best matches with their tool names, methods and parameters'). That return detail implicitly distinguishes it from cloud_call/cloud_describe as a discovery step, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: mentioning that results come back as tool names suggests this is the lookup step to run before invoking an operation. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. cloud_catalog vs cloud_search).

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