Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm org or scope

npm_org_get
Read-onlyIdempotent

Fetch an npm org or scope profile by name, including the account type npm stores, to verify organization details before publishing or auditing packages.

Instructions

Get an npm org or scope profile, including the type npm actually stores. Requires 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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_org_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. npm org or scope name, e.g. `babel`. Case-sensitive.
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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one piece of behavioral context beyond that, 'including the type npm actually stores', signaling that the org-vs-scope distinction is surfaced rather than normalized, but it does not explain what that type means or what fields come back.

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 with the resource stated first, so the reader gets the essentials immediately. The second sentence ('Requires `name`') is redundant with the schema's required array, costing a little efficiency.

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?

This is a simple read-only lookup with full schema coverage, rich annotations, and no output schema, so the description does not need to explain return values. The only residual gap is that 'the type npm actually stores' is left unexplained, which slightly weakens an otherwise sufficient definition.

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 already documents case sensitivity, the 214-character limit, and the purpose of context, llm_model, and conversation_id. The description contributes nothing beyond repeating that `name` is required, so the baseline of 3 is 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?

States a specific verb and resource: get an npm org or scope profile. It is distinguishable from npm_org_packages_list and npm_user_get by resource type, though it never names a sibling or exclusion 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 when-to-use guidance: no mention of when to choose this over npm_org_packages_list, npm_user_get, or npm_package_get, and no prerequisites or exclusions. The only guidance, 'Requires `name`', merely restates a schema-level requirement.

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