Skip to main content
Glama
Sign In
sprrint

sprrint

by ejasmuhamed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sprrint_blackhole_list

List open tasks in the Black Hole that have not been assigned to any sprint. Use this to find unscheduled work and decide what to plan next.

Instructions

List unsprinted open tasks in the Black Hole.

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_blackhole_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The verb 'List' communicates a non-mutating read operation, and the qualifiers 'unsprinted open tasks' describe the result set. However, there are no annotations, and the description does not explain the meaning of 'unsprinted,' sorting, pagination, or how the project parameter affects results.

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 a single front-loaded sentence with no filler. It communicates the core operation efficiently and does not repeat structural information already present in the schema.

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?

For a tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It omits the meaning of 'unsprinted' and entirely ignores the project parameter, leaving important calling context to inference.

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

Parameters1/5

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

Schema description coverage is 0%, and the description never mentions the single 'project' parameter. The agent cannot tell whether project filters results, scopes the query, or is ignored. The description fails to compensate for the schema's complete lack of parameter documentation.

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?

The description uses a specific verb and resource: 'List unsprinted open tasks in the Black Hole.' This clearly distinguishes it from mutating black hole siblings like sprrint_blackhole_pull and sprrint_blackhole_drop. However, 'unsprinted' is unexplained and the description does not distinguish it from the broader sprrint_tasks_list tool.

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 versus alternatives such as sprrint_tasks_list, sprrint_blackhole_pull, or sprrint_blackhole_drop. No context, prerequisites, or exclusions are provided.

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