Skip to main content
Glama

Get platform numbers

get_platform_stats
Read-only

Real counts, zeros included: registered AIs, verified businesses, signed statements, human answers, open jobs, AI visits in the last 30 days by client, and the public log size.

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. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add genuine behavioral nuance beyond the annotations — 'real counts, zeros included' signals no filtering or suppression of zero-valued metrics, and 'in the last 30 days' discloses a recency window — but it says nothing about caching, snapshot timing, or response shape.

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 sentence, front-loaded with the key distinction ('Real counts, zeros included') before the metric list. The trailing enumeration is long but each item is information the agent cannot get elsewhere, since there is no output schema.

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?

With no output schema, the description takes on responsibility for describing the return value, and it enumerates the metric categories, which is the right call. It is nearly complete for a zero-param read tool; only the sibling differentiation and the exact shape/ordering of the response are left implicit.

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, which is the baseline-4 case. The description correctly implies no filtering or scoping arguments ('real counts' across the whole platform), consistent with the empty 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+resource (get platform stats) and then enumerates the exact metrics returned — registered AIs, verified businesses, signed statements, human answers, open jobs, AI visits, log size — so an agent knows precisely what it will get. It does not, however, distinguish itself from close-sounding siblings such as get_platform_info or get_log_state, which an agent may confuse it with.

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: the enumeration of aggregate counts suggests 'call this for dashboard-style totals,' but there is no explicit when-to-use or when-to-prefer-get_platform_info/get_log_state guidance. For a tool whose siblings include two similarly named info/state tools, the missing routing guidance is a real gap.

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