Skip to main content
Glama
cloud-mcp
by AVert

cloud_call

Destructive

Execute provider operations by routing flat arguments to the correct path, query, header, or body fields; require confirm for write, destructive, or paid calls.

Instructions

Execute an operation. Flat args are routed to path/query/header/body by the operation schema; 'confirm': true is required for write/destructive/paid

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": {
      "provider": "<provider>",
      "tool": "<tool>"
    },
    "name": "cloud_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
confirmNorequired for writes
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description is consistent with them by requiring an explicit confirm for write/destructive/paid operations. The argument-routing disclosure (flat args distributed into path/query/header/body) is genuinely useful behavior beyond the annotations, but there is no mention of failure modes, partial execution, or what happens if confirm is omitted.

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?

Two dense sentences with the operational constraint placed after the core mechanic; nothing is padded. It is terse to the point of being cryptic, but every clause carries information.

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 destructive, open-world dispatcher with arbitrary passthrough parameters and no output schema, the definition is thin: it omits how to obtain valid provider/tool values, what a successful response contains, and how errors or denied confirms are surfaced. Only the confirm gate and arg routing are covered.

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 only 33%, so the description must carry weight; it does explain how arbitrary extra parameters are interpreted (routed by the operation schema), which addresses the additionalProperties:true ambiguity. However, the two required parameters, provider and tool, are never explained in the description, leaving the most important arguments undefined.

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

Purpose2/5

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

"Execute an operation" is close to a restatement of the tool name; the only specificity is the mechanical note that flat args are routed to path/query/header/body. Nothing states what kind of operations are reachable or how this differs from cloud_describe or cloud_search, so an agent cannot tell when this is the right entry point.

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 only rule offered is a precondition ("'confirm': true is required for write/destructive/paid"), which is a call-time gate rather than usage guidance. There is no indication of when to prefer cloud_call over the catalog/describe/search siblings, nor any prerequisites such as needing a valid provider/tool identifier first.

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