Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

hugging-face-2.hugging_face_status

Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses operational behavior that the annotations do not cover: the free tier's daily per-caller quota, the fact that args are none, and the crucial instruction that payment credentials go in MCP request headers (X-Payment, X-Payment-Tx, Bearer fg_…) rather than in parameters. It also lists what the response contains, which matters because there is no output schema.

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 substance is front-loaded and the key constraint (metadata-only, free quota, header-based payment) is easy to find. However, the same content is repeated in the Chinese and English versions plus a bilingual vendor line, so roughly the same information appears three times; this padding dilutes rather than clarifies.

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

Completeness5/5

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

For a zero-parameter, read-only status tool with no output schema, the description covers what it returns, that it is free with a quota, and how authentication and payment must be supplied. There is nothing further an agent would need in order to call it correctly.

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 tool has zero parameters, which sets the baseline at 4, and the description reinforces this by explicitly stating '入参:无' / 'Args: none'. It does not add further parameter meaning, but none is needed.

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 states a specific behavior: it returns only snapshot metadata and enumerates exactly what that metadata contains (record count, collection time, SHA-256, primary key and schema), plus the stated purpose of confirming the data version. It is clearly a read-only metadata check rather than a data retrieval, though it never names hugging_face_digest or explains how the two differ.

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 an implied use case — confirming the data version — along with the fact that the tool takes no arguments and is subject to a free per-caller daily quota. There is no explicit when-not guidance and no statement of when to prefer this over the companion digest tool, so the agent must infer the split.

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.