Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

ai-web3-2.ai_web3_digest

Read-onlyIdempotent

免费:AI × Web3 学术研究文献索引 的元数据与固定 20 条样本,用于核对字段口径与采集时间;不含完整记录。

[zh] 供应方资产「AI × Web3 学术研究文献索引」免费(每日限额按调用方计)。 入参:无。 [en] Vendor asset "AI × Web3 学术研究文献索引". 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": "ai-web3-2.ai_web3_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered; the description goes well beyond them. It discloses a daily per-caller quota (rate-limit behavior), that only 20 fixed records are returned rather than the full dataset (a significant data-completeness caveat), and exactly where payment/auth credentials must go — X-Payment / X-Payment-Tx / Authorization: Bearer fg_… in MCP headers, not in parameters. Those are the traits 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.

Conciseness3/5

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

Key facts are front-loaded, but the same content is restated three times across the lead paragraph, the [zh] line and the [en] line — 'free' and 'no args' each appear twice, and the header note duplicates the free notice. The bilingual mirroring serves a purpose, yet the definition could be roughly half its length without losing 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 zero-parameter, no-output-schema tool whose annotations already cover the safety profile, the description supplies what's actually needed: the dataset is a 20-row sample, it is quota-limited, and auth travels in headers. The only meaningful omission is how this digest relates to the sibling digest/status tools, which would complete the routing picture.

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 schema has zero properties, and the description correctly confirms '入参:无' / 'Args: none', so there is nothing to disambiguate. The baseline for zero-parameter tools is a 4, and no param-level meaning is missing.

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 ('AI × Web3 学术研究文献索引') and states precisely what portion is returned: metadata plus a fixed 20-record sample, explicitly excluding full records. That is far more specific than a tautology. It loses a point because it never mentions the sibling 'ai-web3-2.ai_web3_status', so an agent cannot tell from the text alone which of the two to pick for status vs. data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clearly framed: the sample exists '用于核对字段口径与采集时间' (to verify field definitions and collection time), which tells the agent this is a preview/schema-check call rather than a data pull. The '不含完整记录' clause is an explicit scope exclusion. It stops short of naming an alternative to use when full records are actually needed, leaving that inference to the agent.

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.