Skip to main content
Glama

SMM panel market totals

market_stats
Read-onlyIdempotent

Totals across the index: panels listed and how many of them have live prices read, platforms, canonical services, listings, and the cheapest quotable rate. Quote a price figure with the priced-panel count, not the listed total.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds the meaningful caveat that listed panels and priced panels differ and that the priced-panel count is the correct denominator. It does not disclose freshness/latency of the live prices or what happens with zero quotable prices.

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?

One dense sentence enumerating metrics plus a short imperative caution, with no filler. The metric list is long but front-loaded and each item maps to a returned field rather than being padding.

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?

For a no-parameter read-only aggregate tool with no output schema, the agent still needs to know the shape of the response and units, which the description only partially implies. The priced-versus-listed caveat is valuable, but field names and rate format remain undisclosed.

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?

There are zero parameters and schema coverage is 100%, so baseline 4 applies. The description adds interpretive meaning to the returned fields, defining 'listed' versus 'priced' panels and the cheapest quotable rate as the key figure.

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: aggregate totals across the market index (panels listed, panel count with live prices, platforms, canonical services, listings, cheapest quotable rate). It is clearly distinguishable from siblings like get_price_index and compare_service_prices, though it doesn't explicitly name which sibling overlaps.

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?

The closing sentence gives one usage cue – quote a price figure with the priced-panel count, not the listed total – which implies this tool is the source for headline market statistics. However, it never states when to prefer get_price_index or compare_service_prices, nor any when-not conditions.

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