Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub user events

github_user_events
Read-onlyIdempotent

List a GitHub user's public events with event type, repository, and timestamp; private events are excluded so you can inspect only the public activity feed.

Instructions

List a user's public events with the event type, repository, and time; private events are never included, only the public feed. Costs 1 core call. Returns {items[{type, repo, created_at}], page, per_page, has_more, next_page}.

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": {
      "user": "<user>"
    },
    "name": "github_user_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
userYesGitHub user login, like octocat (alphanumerics and hyphens)
freshNoBypass the local cache
per_pageNoItems per page, 1-100, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new context: private events are never returned, and each call consumes one core of rate-limit budget.

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 compact sentences: capability and scope first, then cost and return shape. No filler, though the return-shape listing is dense and could have been separated for readability.

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, the description usefully supplies the response shape (items, page, per_page, has_more, next_page), and it discloses the rate-limit cost and public-only scope. Only minor gaps remain, such as cache behavior, which the schema's 'fresh' parameter already covers.

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 user, page, per_page, and fresh are all already documented with formats and ranges. The description adds nothing about parameter behavior, which is acceptable at full schema coverage — baseline 3.

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 ("List a user's public events") and enumerates the fields returned (event type, repository, time). The explicit public-only scope separates it from tools that could return broader user data, though no sibling is named directly.

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 public-feed constraint implies when this tool is and isn't appropriate, and the "Costs 1 core call" note helps an agent budget calls. However, there is no explicit when-to-use guidance or named alternative for private activity or repo-level event data.

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