Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

stack-overflow-2.stack_overflow_status

Read-onlyIdempotent

免费:仅返回快照元数据(记录数、采集时间、SHA-256、主键与 schema),用于确认数据版本。

[zh] 供应方资产「Stack Overflow 开发者问答索引」免费(每日限额按调用方计)。 入参:无。 [en] Vendor asset "Stack Overflow 开发者问答索引". Free (daily per-caller quota). Args: none. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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": "stack-overflow-2.stack_overflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), yet the description adds real context beyond them: a free tier with a daily per-caller quota, the exact fields returned, and — importantly — that payment credentials travel in MCP headers (X-Payment / X-Payment-Tx / Authorization: Bearer fg_…) rather than in parameters. That auth-mechanism note is the kind of detail an agent would otherwise get wrong.

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?

Short and front-loaded: the return content and purpose come first, followed by quota and auth placement. The zh/en mirroring adds length but each block carries the payment-header warning that matters for invocation, and no sentence is filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what comes back. What is left vague is the quota's practical effect (what happens on exhaustion, whether a retry is expected) and the absence of any pointer to the sibling that serves the actual records.

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?

Zero parameters, so the baseline is 4; the description correctly states "入参:无 / Args: none", confirming no argument construction is needed. It also usefully warns that payment material must not be placed in parameters, which prevents a schema-shape error.

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 states a specific purpose: it returns only snapshot metadata (record count, capture time, SHA-256, primary keys and schema) to confirm the data version. That distinguishes it implicitly from a data-returning sibling like stack_overflow_digest, though it never names that sibling. It is clearly a status/metadata endpoint, not a data fetch.

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?

"用于确认数据版本 / used to confirm the data version" implies the when-to-use case, but there are no explicit exclusions and no named alternative for actually retrieving the dataset. An agent can infer this is a cheap precondition check, but must guess where to go next.

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.