Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user_activity

Retrieve a GitHub user's public contribution activity by handle or profile URL, defaulting to the current year and paging one month at a time.

Instructions

github: Activity. GET /v1/github/user/activity. Provide one of: handle, url. Get public GitHub profile contribution activity for a user. Defaults to the current year and returns one month at a time. 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_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub user URL, e.g. https://github.com/kentcdodds.
yearNoWhen provided, returns profile contribution activity for that year. Defaults to the current year.
cursorNoCursor from the previous response. Pages backward by month through the selected year.
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, the description carries the full burden and does well: it discloses the pagination model (one month at a time, cursor pages backward through the selected year) and unusually detailed cost semantics — 1 credit on success, free on errors/cache hits/blocked requests. Gaps remain around behavior when both handle and url are supplied and whether authentication is required.

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?

The substantive content is front-loaded and dense: purpose, parameter rule, defaults, paging, then cost. The leading fragments 'github: Activity. GET /v1/github/user/activity.' restate the name and route without adding meaning, and the cost sentence is long, but nothing is wasted overall.

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 4-parameter read tool with no annotations and no output schema, the definition covers the essentials an agent needs: how to identify the user, year scope, how to page, and billing implications. It stops short of describing the shape of the returned activity data, which matters slightly more given there is no output schema.

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 baseline is 3. The description does add one thing the schema does not: the mutual-exclusivity/or-one-of requirement between handle and url, since neither is marked required. Otherwise year and cursor meaning is already documented in the schema.

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 GitHub profile contribution activity for a user', reinforced by the route GET /v1/github/user/activity. It does not, however, distinguish itself from the sibling github_user_contributions, which sounds like it could return similar data, so the agent must guess between 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 gives a real invocation constraint ('Provide one of: handle, url') and notes the year default and month-at-a-time paging, which implies how to iterate. But it never says when to choose this over github_user, github_user_contributions, or other profile tools, and there are no exclusions.

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