Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face dataset statistics

hugging_face_datasets_statistics_get
Read-onlyIdempotent

Retrieve per-column statistics for a Hugging Face dataset split using owner and repository name to inspect data distributions and quality.

Instructions

Get per-column statistics of a Hugging Face dataset split. Requires owner and name.

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": {
      "owner": "<owner>",
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_datasets_statistics_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Repository name, without the owner.
ownerYesRequired. Owner of the repository: a user or organization name.
splitNoSplit name, e.g. `train`. Default: the subset's first split. An unknown name is refused with a 400.
configNoSubset (config) name, e.g. `plain_text`. Default: the dataset's first subset. An unknown name is refused with a 400.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and mutability are covered. The description adds the scope (per-split, per-column) but says nothing about cost, latency, or size of the result for large datasets — meaningful context for an open-world read. With annotations doing the heavy lifting, a 3 is appropriate.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action. The second sentence is largely redundant with the schema's required array, which is the only minor waste.

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 simple read tool with full schema coverage and rich annotations, the essentials are present, but there is no output schema and the description never says which statistics are returned (counts, means, quantiles?) or how they are shaped per column. That gap matters for deciding whether to call this or fetch rows and compute locally.

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 schema itself documents defaults and the 400 behavior for unknown split/config names. The description only repeats that owner and name are required, adding no meaning beyond the schema, so the baseline 3 applies.

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 verb and resource: 'Get per-column statistics of a Hugging Face dataset split.' An agent can distinguish this from rows_list or viewer_get by the word 'statistics'. It stops short of naming a sibling or explaining how the statistics differ from viewer data, so it is clear but not fully differentiated.

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?

The only guidance is a restatement of required fields ('Requires `owner` and `name`'). There is no statement of when to prefer this over hugging_face_datasets_rows_list or hugging_face_datasets_viewer_get, and no mention of prerequisites such as the split/config needing to exist for statistics to be computable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools