Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

hugging-face-2.hugging_face_digest

Read-onlyIdempotent

免费:Hugging Face 开源模型生态索引 的元数据与固定 20 条样本,用于核对字段口径与采集时间;不含完整记录。

[zh] 供应方资产「Hugging Face 开源模型生态索引」免费(每日限额按调用方计)。 入参:无。 [en] Vendor asset "Hugging Face 开源模型生态索引". 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": "hugging-face-2.hugging_face_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, but the description adds genuinely new operational facts: free tier with a daily per-caller quota, a hard 20-record sample cap, and that payment/auth credentials (X-Payment / X-Payment-Tx / Bearer fg_…) belong in MCP headers, not arguments. That quota-plus-auth-channel detail is exactly what annotations cannot convey.

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 key facts (free, 20-sample cap, no args) are front-loaded, but the same content is restated in the free-tier sentence and again in the [zh]/[en] pair, and the auth-header warning is tacked on at the end. It is functional but carries noticeable duplication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, read-only tool with no output schema, it covers cost, quota, result size and auth placement, which is most of what an agent needs. It does not describe the shape of the returned sample records or how collection time is exposed, which is the one gap the description itself claims to serve.

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 confirms "入参:无" and pre-empts the common failure mode of an agent stuffing payment tokens into parameters. No additional per-parameter semantics are needed or 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?

States a specific resource ("Hugging Face 开源模型生态索引") and what the tool returns: metadata plus a fixed 20-record sample, explicitly "不含完整记录" (not full records). That last clause usefully distinguishes it from a full-record or status-style sibling, though the verb is implicit ("provides/indexes") rather than named directly.

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 a use case ("用于核对字段口径与采集时间" – to verify field definitions and collection time) and an implicit boundary (sample only, not complete records). However, it names no alternative tool and never says when an agent should skip this and call a fuller or different endpoint, leaving selection to inference from sibling names.

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.