Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get GitHub contribution graph

github_profile_contributions_get
Read-onlyIdempotent

Fetch a GitHub user's yearly contribution graph to analyze activity patterns, commit consistency, and engagement over time.

Instructions

Get the contribution graph for a GitHub profile for a given year. Requires handle.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "github_profile_contributions_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year for the contribution graph. Default: current calendar year.
handleYesRequired. GitHub username to look up, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered without the description. The description adds little beyond the year scope: it does not say whether private contributions are included, what the graph contains, or how a profile with no contributions is handled.

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?

Two short sentences with the resource and scope front-loaded and no wasted clauses. The second sentence ('Requires `handle`') duplicates what the required-field list already conveys, so it earns little of its space.

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 simple read tool with no output schema, the definition is minimally adequate but leaves the return shape unspecified - an agent cannot tell whether it gets daily counts, a calendar grid, or a total. Given no output schema exists, at least a hint about the returned structure would close the gap.

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%, including the year default and the @-prefix tolerance for handle, so the description need not carry parameter detail. It restates only the handle requirement and adds no format or range meaning beyond the schema; 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?

States a specific verb and resource: 'Get the contribution graph for a GitHub profile', scoped by year. That distinguishes it in substance from the sibling profile and activity tools, but the description never names an alternative, so the differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite 'Requires `handle`', which merely restates the schema's required field. Nothing says when to choose this over github_profile_get or github_profile_activity_list, or when the year scoping matters.

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