Skip to main content
Glama

Physical Capability Cloud

get_top_demand

Read-only

Get demand aggregated by capability type. The gateway doesn't publish demand yet: it answers an empty list marked suppressed.

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": "get_top_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of top demand entries to return (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), and the description adds important context beyond them: the gateway doesn't publish demand yet, so the call returns an empty list marked `suppressed`. That prevents an agent from mistaking an empty result for a bug. It does not describe the shape of a populated entry, keeping it below a 5.

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

Conciseness5/5

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

Two short sentences, front-loaded with the purpose, followed immediately by the current-state caveat. Nothing is redundant and nothing could be cut without losing meaning.

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 single optional-parameter read tool with annotations and no output schema, the description covers purpose and current return behavior. The only gap is that it never describes what a populated demand entry looks like once the gateway does publish data.

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 100% and the single `limit` parameter carries its own default and meaning, so the schema does the heavy lifting. The description adds no further detail about how `limit` interacts with the currently suppressed results. Baseline 3 applies.

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: get demand aggregated by capability type. An agent knows exactly what is being retrieved. It does not name or contrast itself with the plausible sibling submit_demand, so it stops short of a 5.

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 explicit when-to-use, when-not-to-use, or alternative is given. The note that the gateway doesn't publish demand yet is a caveat about results, not guidance about selecting this tool over siblings like submit_demand or get_active_telemetry.

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.