Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_pull_requests

Retrieve public pull requests authored by a GitHub user and filter results by creation date using optional since and until parameters.

Instructions

github: Pull Requests. GET /v1/github/user/pull-requests. Get public pull requests authored by a GitHub user. Filter by created date with since and until. 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

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": {
      "handle": "<handle>"
    },
    "name": "github_user_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly return pull requests created on or after this date. Use YYYY-MM-DD.
untilNoOnly return pull requests created on or before this date. Use YYYY-MM-DD.
cursorNoCursor from the previous response. Defaults to 1.
handleYesGitHub username/handle of the user you want pull requests for

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 full burden and does substantial work: it discloses the 'public' scope restriction and an explicit credit cost model (1 credit on success; errors, blocked/timed-out and invalid requests and cache hits free). It does not cover pagination behavior despite a cursor parameter, or any auth/rate-limit constraints.

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?

Purpose is front-loaded in the first three short sentences, and the cost caveats are grouped at the end. The final sentence ('A not-found or empty result is charged only where that operation's published cost says so') is convoluted and borderline circular, costing a point.

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?

Cost and scope are well covered for a simple four-parameter read tool, but with no output schema the description never hints at the shape of returned pull request records or how the cursor pagination surfaces next pages — an agent must discover that empirically.

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%, so the schema already documents handle, since, until and cursor including the YYYY-MM-DD format. The description only echoes the since/until date filtering and adds nothing about the cursor or handle beyond the schema, so baseline 3 applies.

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 verb and resource: 'Get public pull requests authored by a GitHub user', plus the underlying route GET /v1/github/user/pull-requests. That is clearly distinguishable from siblings like github_user_repositories or github_user_activity, though it never explicitly contrasts itself with them.

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?

It states the filtering capability ('Filter by created date with since and until'), which implies when the tool is useful, but gives no explicit when-to-use/when-not guidance and never points to an alternative for, say, all PRs on a repository rather than by an author.

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