Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

ai-web3-2.ai_web3_export

Read-onlyIdempotent

Ask "read AI × Web3 学术研究文献索引 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] 供应方资产「AI × Web3 学术研究文献索引」按次计费 $0.09 USDC(或等值积分)。 入参:无。 [en] Vendor asset "AI × Web3 学术研究文献索引". 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": "ai-web3-2.ai_web3_export"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent/open-world profile, and the description adds substantially more: price point, the exact payment headers (X-Payment / X-Payment-Tx / Authorization: Bearer fg_…), the ciphertext-only public surface, the authenticated private origin, AES-256-GCM decryption licensing, and the failure mode when unpaid. This is exactly the auth/cost/failure context an agent needs and that no structured field supplies.

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 opening English sentence is well front-loaded and carries the key facts, but the body repeats the same $0.09 price and payment-header instruction three times across the English block, the Chinese block, and the [zh]/[en] restatement. The bilingual duplication roughly doubles length without adding information.

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 parameterless, paid, gated export with no output schema, the description covers cost, credential mechanics, where plaintext lives, and what happens without payment. The remaining gap is that it never characterizes the returned payload (record shape, snapshot identity, volume), which matters given there is no output schema.

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 reinforces this by stating "Args: none" and, more usefully, warns that payment credentials belong in MCP request headers rather than in the argument object — a genuine clarification that prevents malformed calls.

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?

Names a specific verb (read/export) and a specific resource ("AI × Web3 学术研究文献索引"), and distinguishes itself from the free-sample tier. It stops short of naming the sibling digest/status tools, so the boundary with ai_web3_digest is left implicit, and it never says what a snapshot actually contains.

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?

Establishes clear preconditions — paid per call at $0.09, valid FeeGate credential required, otherwise the full records are unreadable — which is real usage guidance. However it references a "free sample" alternative without naming the tool that provides it, and gives no explicit when-not-to-use or comparison against the sibling digest/status endpoints.

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.