sprinty

Overview Schema Source Related Servers Discussions Admin

changelog

Preview or export the current SemVer Markdown release notes and return only their file path; sprint close writes the canonical version automatically.

Instructions

Preview or export the current SemVer Markdown changelog and return only its path; sprint_close writes the canonical changelog automatically.

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

Input Schema

Name	Required	Description	Default
`path`	No
`agent_token`	No
`client_agent_id`	No
`claim_generation`	No
`client_session_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.2Oct 23, 2026

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

Changed2 schema fields changedv0.1.17Aug 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / path
```
Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
```
First observedv0.1.9Jun 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: only the path is returned, not the changelog content itself. It omits authorization/claim requirements (agent_token, client_session_id, claim_generation suggest a claim protocol) and whether export overwrites an existing file.

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?

A single compact sentence with the core capability front-loaded and the sibling relationship appended. No filler whatsoever.

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 five undocumented parameters, no annotations, and no output schema, the description is too thin. An agent cannot tell from it how to satisfy the claim/session parameters or how the returned path should be used, which is a real gap given the claim-oriented sibling tools.

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?

Five parameters with 0% schema description coverage, so the description must compensate and largely doesn't. 'Its path' hints that 'path' is an output location, but agent_token, claim_generation, client_agent_id, and client_session_id are entirely unexplained in both schema and description.

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?

States a specific verb (preview/export) and resource (current SemVer Markdown changelog), and explicitly contrasts with sprint_close, a sibling tool. The only gap is that the description doesn't say what selects 'preview' vs 'export' mode, leaving the two behaviors undifferentiated.

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 clause 'sprint_close writes the canonical changelog automatically' implies this tool is for manual preview/export rather than the normal closing flow, which is useful routing context. But it never states a positive when-to-use condition or when preview is preferred over export.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.