Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dashboard_restart

Restarts the follow-along dashboard and returns its URL and port, so agents can reconnect to a live sprint view after a reset.

Instructions

Restart the follow-along dashboard and return its URL and port.

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

Input Schema

NameRequiredDescriptionDefault
agent_tokenNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • 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
  3. Removedv0.1.15
  4. First observedv0.1.9

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description must disclose operational behavior. It mentions returning URL and port but omits downtime, session impact, auth/permissions, idempotency, and whether the restart is disruptive.

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, and the action and return values are stated up front. It is efficiently structured, though extremely minimal for a tool with four undocumented 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?

It covers the action and return values, but with no annotations, no output schema, and 0% schema coverage on four parameters, major unknowns remain. An agent still lacks guidance on auth, parameter meanings, and side effects.

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?

All four parameters lack schema descriptions (0% coverage), and the description does not mention any of them or their roles. An agent cannot infer what agent_token, client_agent_id, claim_generation, or client_session_id should contain.

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 ('Restart') and resource ('follow-along dashboard'), and notes the return values (URL and port). It does not distinguish from the sibling dashboard_info tool, so it falls short of the highest level.

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?

No guidance is given on when to use this tool versus dashboard_info or other dashboard-related siblings, and no preconditions or exclusions are stated. The only implied trigger is the tautological need to restart the dashboard.

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