Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

stack-overflow-2.stack_overflow_export

Read-onlyIdempotent

Ask "read Stack Overflow 开发者问答索引 beyond the free sample" — $0.09 for a per-snapshot AES-256-GCM decryption license. Full original data is kept on an authenticated private origin; the public endpoint serves ciphertext only. Present a valid FeeGate payment credential to the origin detail gateway to receive plaintext. | 付费购买当前快照的解密授权;完整记录仅在认证私有源站,公开面只有密文。需向源站 detail 网关出示平台付款凭证才能取得明文;未付款无法读取全部记录。

[zh] 供应方资产「Stack Overflow 开发者问答索引」按次计费 $0.09 USDC(或等值积分)。 入参:无。 [en] Vendor asset "Stack Overflow 开发者问答索引". Paid per call: $0.09 USDC (or prepaid credits). 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_export"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it states the $0.09 per-snapshot fee, AES-256-GCM decryption, private-origin ciphertext, and the need to present a FeeGate payment credential. It also clarifies that payment headers belong in the MCP request headers, not in parameters, and that unpaid callers cannot read full records.

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

Conciseness2/5

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

The description is heavily duplicated across English and Chinese blocks, repeating the same payment and access details multiple times. The purpose is front-loaded, but the redundancy and payment boilerplate make it considerably longer than necessary.

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 paid export with no parameters and no output schema, the definition covers the critical access model: payment, ciphertext versus plaintext, and header-based credentials. It does not describe the exact return format or snapshot selection beyond 'current snapshot', but the essential behavioral context is present.

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?

With zero parameters, the baseline is 4. The description reinforces this by stating 'Args: none' and further clarifies that payment credentials go in request headers rather than parameters, which is useful additional context.

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 opening line states a specific action and resource: reading the Stack Overflow developer Q&A index beyond the free sample. It is somewhat obscured by payment and encryption framing, but the core purpose is clear and differentiated from a free sample.

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?

Usage is implied by 'beyond the free sample' and the explicit payment requirement, which tells the agent this is for full paid access rather than the free preview. However, it does not explicitly name sibling tools like digest or status or state when to choose them over this export.

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.