Skip to main content
Glama

dashboard_info

Retrieve the local status window address and check whether it is running, so you can connect to or verify the FPGA dashboard.

Instructions

Return the address of the local status window and whether it is running.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. The verb 'Return' does usefully signal a pure query with no side effects, which matters next to control-style siblings such as backend_control and select_board, and it discloses the two pieces of information produced. But it omits what happens when the window is not running (does it start it? return an empty address?), any auth or local-only constraint, and any side effects on the window's lifecycle.

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 short sentence with the returned data front-loaded and no filler, boilerplate, or repetition of the tool name. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-annotation tool with no output schema, the description does name both return fields (address and running state), which is the main thing an agent needs. The one remaining gap is the format of 'address' (URL, host:port, path) and the behavior in the not-running case, which an output schema would otherwise have covered.

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 takes no parameters, so there is nothing for the description to disambiguate; the schema is an empty object at 100% coverage. Baseline 4 applies, with no parameter-related gaps to compensate for.

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 gives a specific verb ('Return') and a specific resource ('the local status window'), plus the exact facts returned: its address and whether it is running. That is enough to distinguish it from siblings like build_status, activity, or report, which concern build/activity state rather than the local status window's endpoint.

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?

There is no when-to-use guidance: nothing says whether this should be called before connecting to the window, as a health check, or only after some other setup. No alternatives are named, and no prerequisite states (e.g. 'returns not-running if the dashboard has not been started') are given.

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