Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_contributions

Retrieve a GitHub user's yearly contribution graph by handle or profile URL for a specified or current year.

Instructions

github: Contributions. GET /v1/github/user/contributions. Provide one of: handle, url. Get a user's GitHub contribution graph for a year. 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_contributions"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub profile URL
yearNoContribution graph year. Defaults to the current year.
handleNoGitHub handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers: the HTTP route, a detailed credit-cost model (1 credit on success, free for errors/blocked/timeout/invalid/cache hits, conditional charge for not-found/empty). It omits authentication needs and whether results are cached/fresh, which keeps it from 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.

Conciseness5/5

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

Front-loaded with the resource, then the input constraint, then the cost policy, in that priority order. The endpoint path line is mildly redundant but brief, and the cost paragraph is dense with materially useful information rather than filler.

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 tool with no output schema and no annotations, the description should sketch what the contribution graph returns (daily counts, calendar buckets, totals) and whether an empty year yields an empty result versus an error—especially since the cost policy hinges on "not-found or empty result." Cost and input rules are complete; return-value semantics are not.

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 is 3, but the description adds a constraint the schema does not encode: handle and url are mutually exclusive alternatives ("provide one of"), despite the schema listing no required fields. The year parameter's default is already in the schema, so no further credit there.

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?

Names a specific verb and resource: "Get a user's GitHub contribution graph for a year," which is distinct from a general user profile or activity feed. It doesn't explicitly contrast with siblings like github_user_activity, but the resource is concrete enough for an agent to choose confidently.

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 description adds the identity-input constraint ("Provide one of: handle, url"), which is genuine usage guidance, but it never says when to choose this over github_user_activity or github_user, nor does it state exclusions or prerequisites. Usage is implied by the resource rather than explained.

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