Skip to main content
Glama

cloud_search

Read-only

Find API operations across providers using a free-form query in Russian or English, returning 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
providerNosweb|timeweb|selectel|tilda

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.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=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the index is searched with free-form RU or EN text and returns ranked matches with their tool names, methods and parameters, which is exactly the return-shape information an agent needs given there is no output schema.

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 well-formed sentence, front-loaded with the action and scope, with the result payload appended. No filler, though the return clause could be split or trimmed if brevity were the priority.

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

Completeness4/5

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

For a five-parameter, non-destructive search with no output schema, the description covers what is searched, in what language, and what is returned. It stops short of explaining ranking behavior or the natural follow-up (describe then call), which is the remaining gap.

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 80%, so the baseline is 3. The description adds one real clarification — that the query is free-form and language-agnostic (RU or EN) — but says nothing about top (ranking cut-off), kind, product, or provider, leaving those to the schema.

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?

States a specific verb and resource: "Find API operations across providers by a free-form query," plus what comes back (tool names, methods, parameters). That clearly separates it from execution-oriented siblings like cloud_call, though it never names an alternative directly.

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: an agent can infer this is the discovery/entry point before cloud_describe or cloud_call, but the description never says when to prefer it over cloud_catalog or cloud_providers, nor any exclusion or prerequisite.

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