Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_following

Retrieve public GitHub accounts a user follows by supplying a handle or profile URL, with cursor-based pagination to continue through results.

Instructions

github: Following. GET /v1/github/user/following. Provide one of: handle, url. Get public accounts a GitHub user follows. 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_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub profile URL
cursorNoCursor from the previous response. Defaults to 1.
handleNoGitHub handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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 does disclose a non-obvious behavioral trait: the credit-charging model, including that errors, timeouts, invalid requests and cache hits are free. It still omits auth requirements, rate limits, and whether pagination is required to get complete results, so it stops short of full transparency.

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?

The purpose sentence is buried after a namespace prefix, a raw route string, and a parameter rule, so the definition is not front-loaded. The two-sentence cost explanation is informative but could be compressed; nothing is outright wasted, but ordering hurts scannability.

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 three-parameter read tool with no output schema and no annotations, the description covers purpose, the handle-or-url requirement, and the cost model adequately. It does not describe the shape of returned account data or how cursor paging terminates, which are minor gaps given the 100% schema coverage of parameters.

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 the baseline would be 3, but the description adds a constraint the schema does not express: although zero parameters are marked required, the caller must supply exactly one of handle or url. That is genuine added meaning beyond the structured fields.

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 gives a specific verb and resource: 'Get public accounts a GitHub user follows', which is meaningfully distinct from the sibling github_user_followers. It does not name that sibling explicitly to draw the contrast, so an agent must infer the following-vs-followers distinction from wording alone.

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 'Provide one of: handle, url' line tells the agent how to invoke the tool, and the cost paragraph implies the tool is fine to call freely on cache hits. However, there is no explicit when-to-use framing or named alternative for related lookups such as github_user_followers or github_user, so usage guidance is only implied.

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