Skip to main content
Glama

FoxAPIs data sources

GitHub user

github_user
Read-onlyIdempotent

A public GitHub profile: followers, repositories, bio and account age, from the user name. Costs 1 credit 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": {
      "user_id": "<user_id>"
    },
    "name": "github_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesFor example: "torvalds"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: a 1-credit cost per call, no charge when no data comes back, and a FoxAPIs key requirement. It stops short of saying what an empty/no-data response looks like.

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?

Three short sentences, front-loaded with what the tool returns, then cost, then auth. All are load-bearing, though the parenthetical '(free to start)' is promotional filler rather than decision-relevant information.

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 single-parameter read tool with no output schema, the description does the needed work: it sketches the return shape, states the cost model, and names the auth prerequisite. Nothing an agent must know to invoke it correctly is missing.

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 coverage is 100% and the schema already supplies the 'torvalds' example for user_id. The phrase 'from the user name' confirms the parameter is a login handle rather than a numeric ID, but that is only a marginal addition over the structured field.

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 ('public GitHub profile') and enumerates the payload it returns (followers, repositories, bio, account age) keyed by username. That distinguishes it implicitly from github_repo and github_search, but it never names a sibling to sharpen the boundary.

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?

'from the user name' implies the precondition for calling, and the credit/auth notes signal this is a paid external lookup. There is no explicit when-to-use versus github_search or github_repo, so the agent must infer the routing 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.

Resources