Skip to main content
Glama

AutoTasker Hub — China Social Data API

content_factory_stats

Content factory metrics: generated assets, batches, per-language breakdown. $0.01 USDC.

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": "content_factory_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?

No annotations exist, so the description bears the full behavioral burden. It does disclose a genuinely useful behavioral fact not in any structured field: the tool costs $0.01 USDC, implying a paid/paywalled call. However, it says nothing about payment mechanics, freshness of the metrics, or the shape of the return payload, which matters given there is no output schema.

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 terse fragments, front-loaded with what the tool returns and followed by the cost. Every clause carries information; nothing is padded or repeated.

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 zero-parameter stats tool with no output schema, listing the metric categories substitutes adequately for a return-value section, and the cost disclosure covers the main surprising behavior. It stops short of stating metric freshness or the time window covered, which an agent would need to interpret the numbers.

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 elaborate and the baseline is 4. The description correctly implies a no-argument, whole-set metrics read rather than inviting filter arguments.

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 the resource (content factory metrics) and enumerates returned content: generated assets, batches, per-language breakdown. That is specific enough to distinguish it from generic stats siblings like chain_stats or bitcoin_fees, though the verb is implicit ('metrics:' rather than 'get'/'retrieve').

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 guidance on when to call this versus alternatives, no preconditions, and no note about what questions it answers. The only contextual sentence concerns price, not usage.

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.