Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_repositories

Retrieve public GitHub repositories for a user by handle or profile URL, with sorting, type filters, and cursor-based pagination.

Instructions

github: Repositories. GET /v1/github/user/repositories. Provide one of: handle, url. Get public repositories for a GitHub user. Supports pagination and GitHub's repo sorting options. 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_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub user URL, e.g. https://github.com/kentcdodds.
sortNoSort by created, updated, pushed, or full_name. Defaults to updated.
typeNoRepository type. Defaults to owner. GitHub also supports all and member.
cursorNoCursor from the previous response. Defaults to 1.
handleNoGitHub username/handle of the user you want the repositories for
directionNoSort direction: ascending or descending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclosure burden and does so well: it states pagination support, sorting options, the public-only scope, and a detailed credit-cost model including what is free (errors, blocked/timed-out requests, cache hits). What it omits is the response shape and any note on rate limits or auth, which keeps it short of a 5.

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 and the handle/url requirement are front-loaded, which is good, but the leading "github: Repositories. GET /v1/github/user/repositories." restates the name and endpoint with little added value. The cost paragraph is long and generic boilerplate that could be condensed to one clause.

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 read-only listing tool with no output schema and full schema coverage, the definition covers purpose, the one-of input constraint, pagination, sorting, and cost. The main gap is that nothing describes what a repository result contains, which matters since there is no output schema to fall back on.

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%, so all six parameters (handle, url, sort, type, cursor, direction) already carry their own semantics and defaults. The description adds only the high-level note that sorting options and pagination are supported, which is the correct baseline of 3 when the schema does the heavy lifting.

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 states a specific verb and resource: "Get public repositories for a GitHub user," which distinguishes it from profile-level siblings like github_user or github_user_activity. It is clear and unambiguous, though it does not explicitly name a contrasting sibling such as github_trending_repositories.

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?

Usage context is implied by "for a GitHub user" and constrained by "Provide one of: handle, url," which tells the agent how to invoke it. However, there is no explicit when-to-use versus when-not-to-use guidance, and no alternative tool is named for cases like trending or org repos.

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