Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

ai-web3-2.ai_web3_status

Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description does add genuinely useful behavior beyond them: a free daily per-caller quota (a rate limit) and the exact placement of payment/auth material in MCP headers rather than parameters. It does not say what happens when the quota is exhausted or on payment failure.

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 core value statement is front-loaded, which is good, but the content is then restated across a Chinese block, an English block, and a closing payment note — the 'free / no args' facts are repeated three times. The bilingual splitting aids some readers but bloats the definition compared with what is actually new 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?

Since there is no output schema, the description carries the return-value burden and discharges it by naming every field returned. Auth/header mechanics are also covered. Remaining gaps are quota-exhaustion and error behavior, which are minor for a metadata-only status endpoint.

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, and the description reinforces the empty arg list with '入参:无 / Args: none'. It adds the important detail that payment and auth credentials belong in the transport headers, not in the argument object, which prevents an agent from trying to construct a payment parameter.

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 gives a concrete verb+resource: it returns ONLY snapshot metadata, and it enumerates the fields (record count, collection time, SHA-256, primary keys, schema) so the agent knows exactly what comes back. The '仅' (only) qualifier implicitly separates it from the sibling digest tool that serves actual data, though it never names that sibling explicitly.

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?

It states the use case directly — '用于确认数据版本' (to confirm the data version) — which tells the agent when to reach for this versus fetching content. It also supplies cost/quota context (free, daily per-caller quota) and notes that there are no args. It stops short of naming an explicit when-not or a named alternative.

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.