Telemetry Machine

Get dashboards

get_dashboards

Read-only

List dashboards, or get one with its tiles, through the Telemetry Machine REST API (https://telemetrymachine.com/docs/api.md).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "get_dashboards"
  }
}

Input Schema

Name	Required	Description
`id`	No
`body`	No	The JSON body the action takes.
`limit`	No
`action`	Yes
`offset`	No
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedInput schema / properties / body / additionalProperties
```
Previous value: -{}New value: +true
```
First observedOct 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation. The description adds that the get mode returns a dashboard with its tiles and points to the REST API documentation, but it does not cover pagination behavior, filtering semantics, or error handling.

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?

The definition is a single front-loaded sentence with no wasted wording. The API documentation link is compact and directly relevant.

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 six-parameter tool with a nested body and no output schema, the description is too sparse. It omits parameter behavior, pagination details, and return-shape information beyond mentioning that get includes tiles.

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?

Schema description coverage is only 17% across six parameters, including a nested body object. The description clarifies the action modes but does not explain id, body, limit, offset, or search semantics, so it does not compensate for the documentation gap.

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?

The description uses specific verbs and resource: list dashboards or get one with its tiles. It clearly distinguishes the two supported modes and is not tautological with the title.

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?

It implies when to use list versus get by saying 'List dashboards, or get one with its tiles.' However, it gives no explicit guidance about when to choose this tool over the sibling edit_dashboards or other read tools, and it provides no exclusions or alternatives.

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

All Telemetry Machine tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?