Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

info

Provides startup orientation and compact sprint discovery for sprinty, helping AI coding agents review available sprints before binding to one.

Instructions

Startup orientation and compact sprint discovery before binding to one sprint.

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

Input Schema

NameRequiredDescriptionDefault
git_dirNo
data_dirNo
agent_tokenNo
workspace_dirsNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / agent_token
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / claim_generation
      Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / client_agent_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / client_session_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. Addedv0.1.17

TDQS

C2.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 carries the full behavioral burden. 'Orientation' and 'discovery' imply a read-only operation, but it does not state whether the tool mutates state, what authentication/token requirements exist, or what side effects the seven parameters may trigger.

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 a single front-loaded sentence with no filler. It is concise, though its terseness contributes to the ambiguity around scope and parameters.

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 seven-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is far too thin. It provides a high-level orientation but leaves the caller without enough information to invoke it correctly or understand its result.

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 there are seven parameters, yet the description explains none of them. It adds no meaning for git_dir, data_dir, agent_token, workspace_dirs, client_agent_id, claim_generation, or client_session_id.

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 indicates a startup orientation and sprint discovery tool, but the verb/resource are vague: 'info' is generic and 'startup orientation' does not specify what is returned or what operation is performed. It hints at timing relative to sprint binding but does not clearly distinguish itself from siblings such as overview, dashboard_info, or next.

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?

It gives a clear usage context: use at startup before binding to one sprint. However, it does not name alternatives, when-not conditions, or prerequisites, so the routing guidance is incomplete but not 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