Skip to main content
Glama
Sign In
sprrint

sprrint

by ejasmuhamed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sprrint_overview

Get a workspace overview: view greetings, counts, active sprints, and tasks that need a nudge.

Instructions

Workspace home: greeting, counts, active sprints, and tasks that need a nudge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It does name the returned categories (greeting, counts, active sprints, nudged tasks), which is useful context. It does not explicitly state whether the call is read-only or mention how 'nudge' tasks are determined.

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 a colon-delimited list of contents. Every word earns its place and there is no verbosity or redundancy.

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 zero-parameter overview tool, the description conveys the main output areas. However, there is no output schema and no guidance on how 'counts' are scoped nor what makes a task 'need a nudge', and the overlap with sprrint_home is left unresolved.

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

Parameters4/5

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

The tool has zero parameters, so the default baseline of 4 applies; there are no parameter semantics the description needs to explain. The description instead focuses usefully on what the overview contains.

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 names a concrete resource ('Workspace home') and specifies the output contents: greeting, counts, active sprints, and tasks needing a nudge. This makes the tool's purpose clear, but it does not differentiate it from the sibling tool sprrint_home, which appears to serve a similar role.

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 phrase 'Worksapce home' implies this is a dashboard/starting-point tool, so a basic usage context is inferable. However, there is no explicit guidance about when to choose this over sprrint_home, sprrint_activity, or sprrint_now, nor any exclusions.

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