Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

platform_stats

Read-onlyIdempotent

Feegate 平台自身运营指标(按次计费 $0.005 USDC 或等值积分,30 天窗口):真实访问量、独立访客、AI 爬虫 / 搜索引擎抓取明细(哪家 AI 来抓过、抓了多少次)、热门页面、地区分布。衡量'这个市场有没有真实 Agent 流量'时用。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious operational context beyond them: metered billing of $0.005 USDC (or equivalent credits) per call, and a fixed 30-day data window. It does not describe response shape or rate limits, 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.

Conciseness4/5

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

A single dense sentence that front-loads the core identity (platform's own operational metrics) before the pricing/window parenthetical and the enumeration of returned data. The item list is long but each entry is a distinct data category, so little is wasted; the trailing usage clause is well placed.

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 parameters and no output schema, the description carries the burden of describing what comes back, and it does so by enumerating the five metric families. Combined with the disclosed cost and 30-day window, an agent has enough to decide and call. Return format and pagination/limits remain unspecified, which is the only notable 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 no parameter semantics to clarify and the baseline of 4 applies. The description correctly implies that all scoping (time window) is fixed server-side rather than caller-controlled.

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 a specific resource (Feegate platform's own operational metrics) and enumerates exactly what it returns: visit volume, unique visitors, AI crawler/search-engine crawl breakdown, popular pages, and geographic distribution. That is far more concrete than the bare name 'platform_stats', though there is no explicit verb and no sibling is named as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It closes with an explicit use case: use this when measuring whether 'this market has real Agent traffic'. That gives the agent a clear decision criterion rather than leaving usage to inference. It does not state when not to use it or point to an alternative tool, so it stops short of a 5.

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.