Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_followers

Retrieve public followers for a GitHub user by username or profile URL, with cursor pagination for browsing results.

Instructions

github: Followers. GET /v1/github/user/followers. Provide one of: handle, url. Get public followers for a GitHub user. Pass username, handle, or url. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub user URL, e.g. https://github.com/torvalds.
cursorNoCursor from the previous response. Defaults to 1.
handleNoGitHub username/handle of the user you want the followers for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well on one axis: it discloses credit charging semantics (1 credit on success, free on errors/blocked/timeout/invalid/cache hits, conditional charge on not-found). It says nothing about result ordering, page size, auth requirements, or rate limits, leaving meaningful behavioral gaps.

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

Conciseness3/5

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

Purpose is front-loaded, but the parameter requirement is stated twice in near-identical form ("Provide one of: handle, url" then "Pass username, handle, or url"). The billing sentence is long and could be tightened without losing meaning.

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 three-parameter read tool with no output schema and no annotations, the description covers the call requirement and cost model. It omits what the response looks like (list of user objects, page size, ordering) and how the cursor behaves across pages, which an agent needs to consume results correctly.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds a genuine constraint absent from the schema: at least one of handle or url must be supplied, even though the schema declares zero required parameters. Minor noise: it says "username" although no username parameter exists.

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 public followers for a GitHub user," plus the underlying route GET /v1/github/user/followers. It is clearly distinguishable from siblings like github_user_following or github_user by resource noun, though it never names an alternative explicitly.

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?

Provides the input requirement ("Provide one of: handle, url") which implies usage context, but gives no guidance on when to choose this over github_user_following or github_user, and no prerequisites. Usage is inferable from the name and purpose but not stated.

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