Skip to main content
Glama
Sign In
NitroStack Calculator MCP Server

NitroStack Calculator MCP Server

by harinie-4466
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

fetchJiraNotifications

Fetches recent Jira ticket updates including assignments, comments, and due dates, returning a flattened list of notifications.

Instructions

Fetch recent Jira ticket updates (assignments, comments, and due dates). 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": "fetchJiraNotifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO 8601 timestamp. Only returns notifications created after this time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It states that a flattened list is returned and scopes to recent updates, but does not disclose authorization requirements, rate limits, default time range if 'since' is omitted, or any side effects. 'Fetch' implies read-only but is not explicit.

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 efficient sentences with no unnecessary words. It front-loads the action and resource, making it immediately clear what the tool does.

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?

The description covers the basic purpose and return format, but with no output schema, it lacks details about the structure of each notification. It also omits behavior when 'since' is absent and does not specify limits or ordering, leaving moderate gaps for a relatively simple tool.

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 parameter 'since' has complete schema coverage (100%), so the schema already provides its meaning. The description adds no extra parameter detail, aligning with the baseline of 3 for high schema coverage.

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 a specific verb (Fetch) and clearly identifies the resource (Jira ticket updates) with examples of update types (assignments, comments, due dates). It distinctly marks this as the Jira-specific tool among sibling notification fetchers.

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?

The description provides clear context for when to use the tool (to fetch recent Jira updates) but does not explicitly mention alternatives or exclusions relative to sibling tools like fetchSlackNotifications. The name and sibling list imply usage, but explicit wording like 'for Jira notifications' is absent.

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