Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

stack-overflow-2.stack_overflow_digest

Read-onlyIdempotent

免费:Stack Overflow 开发者问答索引 的元数据与固定 20 条样本,用于核对字段口径与采集时间;不含完整记录。

[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_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description discloses that the tier is free with a daily per-caller quota and that payment credentials must travel in MCP headers (X-Payment / Authorization: Bearer) rather than as arguments. That is genuinely useful operational context the annotations do not carry; the only gap is no mention of response shape or pagination, which is minor given the fixed 20-record cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is front-loaded and the sample-size caveat appears first, but the entire payload is duplicated in Chinese and English, roughly doubling length without adding information. The payment-header note is valuable but tacked on at the end rather than integrated.

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, read-only digest with no output schema, the description supplies what matters: record count (20), what is excluded (full records), cost/quota model, and auth placement. Sufficient for an agent to call it correctly and to know the result will not be exhaustive.

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 and the description confirms this explicitly with '入参:无 / Args: none'. With an empty schema and 100% coverage, no further parameter explanation is required, so it lands at the zero-parameter baseline.

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 concrete resource (Stack Overflow 开发者问答索引) and states exactly what this variant returns: metadata plus a fixed 20-record sample, explicitly excluding full records. This differentiates it from a full-record fetch, though it never mentions the sibling stack_overflow_status tool, so the sibling distinction is only partial.

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?

It gives an intended use — verifying field conventions and collection time — and a clear exclusion (no full records). However, it never says what to call when full records are actually needed, so the agent must infer the alternative rather than being routed to it.

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.