Skip to main content
Glama

NS Pros MCP Gateway

huggingface__hf_whoami

Inspect the current Hugging Face authentication context, including the account, visible organization memberships, and credential access details. Read-only and never returns credential values.

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": "huggingface__hf_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does deliver two valuable behavioral facts: the operation is read-only and it never returns credential values, which reassures an agent it is safe to call. It also qualifies scope with "visible" organization memberships, hinting results may be partial. It does not say what happens when no credentials are configured (error vs. empty result), which is the main remaining gap for an auth-introspection tool.

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?

Two sentences, front-loaded with the action and resource, followed by a short safety note. Every clause adds information (what is inspected, what is included, what is never exposed) with no filler or redundancy.

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 zero-parameter, read-only identity tool with no output schema, the description is nearly complete: it tells the agent what category of data comes back (account, organizations, credential access details) and that secrets are excluded. The only meaningful omission is failure behavior when unauthenticated, which an agent would want before calling.

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 takes zero parameters, so there is no parameter semantics to add and the description correctly avoids inventing any. Baseline for a 0-parameter tool applies; the description instead spends its words on the output contents, which is the right allocation.

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 pairs a specific verb ("Inspect") with a specific resource ("the current Hugging Face authentication context") and enumerates the contents: account, visible organization memberships, credential access details. That is far more than a restatement of the name. It does not explicitly distinguish itself from any sibling, though the sibling list contains no other identity/introspection tool, so the risk of confusion is low.

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?

The phrase "current ... authentication context" implies the use case (verifying which account/orgs the credentials belong to) but the description never states when to call it, when not to, or what to do instead. No prerequisites or alternatives are named, so the agent must infer the trigger from the resource itself.

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.