sprinty

by ebursztein

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

dashboard_info

Retrieve the current dashboard URL and port without starting or restarting the dashboard.

Instructions

Return the current dashboard URL and port without starting or restarting it.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.2Oct 23, 2026

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

First observedv0.1.9Jun 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose the important non-side-effecting nature (no start/restart). It says nothing about authentication via the agent/client tokens, session requirements, or response behavior, leaving significant behavioral gaps for a tool with four credential-like parameters.

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, front-loaded sentence with zero waste; the key constraint (no start/restart) is the last clause and easy to scan.

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 simple info tool this is nearly adequate on the purpose side, but with no annotations, no output schema, and four opaque credential parameters at 0% coverage, the definition omits too much for an agent to call it correctly without guessing at parameter meaning.

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 all four parameters (agent_token, client_agent_id, claim_generation, client_session_id) are completely undocumented in both the schema and the description. The description adds no meaning about any of them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return the current dashboard URL and port') and explicitly scopes out the mutating behavior of the sibling dashboard_restart. An agent can distinguish this read-only info tool from the restart tool without opening either schema.

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?

The phrase 'without starting or restarting it' implicitly routes the agent to this tool when it wants dashboard details without side effects, contrasted against dashboard_restart. However, no explicit 'use when / do not use when' framing or prerequisite conditions are given.

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