Skip to main content
Glama
Sign In
sprrint

sprrint

by ejasmuhamed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sprrint_activity

Retrieve project activity feed filtered by time range, actor, project, type, or search query to track updates across sprints and tasks.

Instructions

Activity feed. tab is you|all. range is 0 (today), 7, 30, or all.

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

Input Schema

NameRequiredDescriptionDefault
qNo
tabNoall
typeNo
actorNo
rangeNo7
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only discloses allowed values for tab and range; it does not describe the response shape, side effects, permissions, pagination, or how the other parameters affect behavior. This is a significant gap for a feed tool.

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?

The description is two short sentences with no fluff. It front-loads the core resource and packs the parameter constraints into a compact form. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters, no output schema, and no annotations, the description is inadequate. It only covers two of six parameters and gives no information about return values or call behavior, leaving too much to inference for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It meaningfully documents two parameters (tab and range) but leaves q, type, actor, and project completely unexplained. This incomplete compensation leaves an agent guessing about the remaining parameters.

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

Purpose3/5

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

The description states the resource (activity feed) and immediately gives two key parameter domains (tab: you|all, range: 0/7/30/all), but it lacks a verb and does not distinguish this from sibling reporting tools like sprrint_overview or sprrint_search. It is more specific than a tautology but still vague.

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?

There is no guidance on when to use this tool instead of alternatives such as sprint_overview, sprint_search, or sprint_home. The parameter hints describe value choices, not the situations that warrant this tool.

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