Skip to main content
Glama
Sign In

GitShine

by com.gitshine
OverviewDiscussionsAdmin

GitHub Wrapped

get_github_wrapped
Read-onlyIdempotent

A GitHub user's year in review: contributions and active days, longest streak, busiest day, month and weekday, top repositories and languages, achievements and a one-line persona.

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": {
      "username": "<username>"
    },
    "name": "get_github_wrapped"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year, from the year the account was created to this year. Defaults to this year.
usernameYesA GitHub username, @handle or profile URL (organizations aren't supported).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real value by disclosing the shape of the returned content, which matters because there is no output schema; it omits any note on cost, latency, or behavior for accounts with sparse data.

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?

A single front-loaded sentence that names the resource first and then the contents, with no filler or repetition. Every clause earns its place by naming a distinct piece of the output.

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?

With no output schema and no annotation for return content, the enumeration of what comes back is exactly what an agent needs, and the schema carries parameter detail. It stops short of noting whether results are cached or what happens for private/empty accounts, but the core is complete.

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 both parameters (username accepting handle/profile URL, year bounded by account creation) are already fully documented in structured data. The description adds no meaning beyond that, which is the expected baseline.

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 ('A GitHub user's year in review') and enumerates the payload: contributions, active days, longest streak, busiest day, top repositories/languages, achievements, persona. It never distinguishes itself from the sibling get_github_stats, so an agent must infer the difference from names alone.

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 is only implied by the 'year in review' framing; there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_github_stats or compare_github_profiles. An agent can guess this is the fun annual-summary tool, but nothing in the text confirms that routing decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GitShine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources