NitroStack Calculator MCP Server

fetchGithubNotifications

Fetch recent GitHub notifications for pull request review requests, CI failures, and mentions. Returns a flattened list, optionally filtered by creation time.

Instructions

Fetch recent GitHub notifications (PR review requests, CI failures, and mentions). Returns a flattened list of notifications.

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": "fetchGithubNotifications"
  }
}

Input Schema

Name	Required	Description	Default
`since`	No	ISO 8601 timestamp. Only returns notifications created after this time.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It discloses that a flattened list is returned and lists some notification categories, but it does not specify the default time window, authentication requirements, rate limits, or side-effect/read-only status. 'Recent' is vague and leaves important behavioral details unstated.

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?

The description is two short sentences with no filler. It is front-loaded with the action and resource, and every word contributes useful information.

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 tool with one optional parameter and no output schema, this description provides the basic purpose and return type. However, it lacks details about the default time interval and the structure of the returned flattened list, leaving some ambiguity for an agent.

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?

The single optional parameter `since` is already fully described in the schema as an ISO 8601 timestamp that filters notifications. The description adds no extra parameter detail, but with 100% schema description coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Fetch' and identifies the resource 'GitHub notifications' with content examples (PR review requests, CI failures, and mentions). This clearly distinguishes it from sibling notification fetchers like fetchSlackNotifications or fetchJiraNotifications.

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

Usage Guidelines4/5

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

While no explicit when-not-to-use or alternative names are mentioned, naming 'GitHub notifications' provides clear context for when this tool is appropriate. The sibling tool names make the intended scope obvious, though an explicit exclusion would strengthen this dimension.

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

Deploy Server