Skip to main content
Glama

FoxAPIs data sources

Hugging Face model

huggingface_model
Read-onlyIdempotent

A Hugging Face model by id: downloads, likes, task, library, licence and last update. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_id": "<model_id>"
    },
    "name": "huggingface_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYesFor example: "bert-base-uncased"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world semantics, and the description adds genuinely useful behaviour: a fixed price of 2 credits per call and a no-charge guarantee when the response is empty. It does not cover error cases, rate limits, or what happens with an unknown id, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short clauses, front-loaded with what the tool returns, followed by cost and auth prerequisites. No redundant or filler wording.

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 one-parameter lookup with no output schema, the description compensates well by naming the returned fields plus the cost and credential requirements. The only gap is unspecified behaviour for a nonexistent or private model id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single model_id parameter already carries an example ('bert-base-uncased'), so the schema does the work. The description only repeats 'by id' without adding format or case-sensitivity details, making the baseline 3 appropriate.

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 specific resource and lookup key ('A Hugging Face model by id') and enumerates the fields returned (downloads, likes, task, library, licence, last update), so an agent knows exactly what it gets. The resource is obviously distinct from siblings like github_repo or academic_paper, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to use this over an alternative (e.g., a repo- or paper-oriented tool), and no exclusions. The credit cost and API-key requirement give an agent decision context, but that is cost/auth information rather than usage guidance.

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.

Resources