Skip to main content
Glama

Platform stats

get_platform_stats
Read-onlyIdempotent

Live counts: service areas, deliveries, agents connected.

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_platform_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/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 safety and repeatability are covered. 'Live counts' adds a bit of behavior (values reflect current state, not a snapshot), but says nothing about freshness, caching, or whether counts are scoped to the authenticated account.

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 short fragment with a colon-delimited list — dense and front-loaded with the key qualifier 'Live'. It's terse to the point of being clipped rather than a full sentence, but nothing is wasted.

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?

No output schema exists, so the description is the only place the return shape could be described, and it gives only three example count names without units, grouping, or whether more fields appear. For a simple zero-param read tool this is close to adequate, but the missing scope/freshness detail leaves a real gap.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to document and the baseline applies. The description does not, however, clarify what the counts cover (whole platform vs. the caller's workspace), which is the only semantic question a zero-param tool leaves open.

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 concrete resources returned (service areas, deliveries, agents connected) and calls them 'live counts', which reads clearly as an aggregate metrics read. It doesn't contrast itself with sibling reads like list_deliveries or list_service_areas, so an agent must infer that this returns counts rather than records.

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 when-to-use guidance, no exclusions, and no mention of the obvious alternative read tools (list_deliveries, list_service_areas) that return the underlying records rather than counts. The word 'Live' hints at a dashboard-style summary use case but never states it.

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.