Skip to main content
Glama

TANDIU AI infrastructure data

Cloud agents compared

list_cloud_agents
Read-onlyIdempotent

Cloud agents (Personal Agents, Work Agents, hosting platforms) with specs and monthly prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cloud_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that—no default page size, no ordering of results, no note on what happens when limit is omitted or how query matches.

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

Conciseness3/5

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

It is a single short fragment with no wasted words and the key content is front-loaded. However, the terseness is under-specification rather than discipline—the parenthetical is doing all the disambiguation work.

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 three-parameter, optional-arg listing tool with no output schema, an agent still needs to know default limit/pagination behavior and query semantics, none of which are given. What exists is accurate but far from sufficient to invoke confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It partially covers the kind parameter by naming the three categories (personal, work, platform), but says nothing about limit (range 1–50, default behavior) or query (what fields it matches against).

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

Purpose3/5

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

The description names the resource and its sub-kinds (Personal Agents, Work Agents, hosting platforms) and says the payload includes specs and monthly prices, so the agent can infer it returns a comparison list. But it is a noun phrase with no verb, and it doesn't explicitly frame this as a listing/lookup operation that differs from siblings like list_llm_prices or list_gpu_prices.

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?

There is no statement of when to use this tool, when not to, or which sibling to choose instead (e.g., list_llm_prices vs. this for agent platforms). Usage is only implied by the resource name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources