Skip to main content
Glama
Sign In

tlly

by dev.tlly
OverviewDiscussionsAdmin

List dashboard versions

list_dashboard_versions
Read-only

List a dashboard's saved versions (newest first) with which one is live and a members-only preview URL for each.

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": {
      "dashboard_id": "<dashboard_id>"
    },
    "name": "list_dashboard_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dashboard_idYesid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral detail beyond annotations: results are ordered newest first, include which version is live, and expose a members-only preview URL. It does not mention pagination or result limits, which keeps it short of a 5.

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 description is a single compact sentence with zero wasted words. The key information is front-loaded: what is listed, ordering, live indicator, and preview URL.

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 read-only list operation with a single required parameter and no output schema, the description covers the return shape well enough: versions are newest first, one is marked live, and each has a members-only preview URL. It lacks mention of pagination or whether all versions are returned, which is a minor completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the schema's description for dashboard_id is only "id", which is not very informative. The description clarifies that the id refers to a dashboard, but adds no syntax, format, or scoping details beyond that.

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 states a specific verb and resource: "List a dashboard's saved versions." It distinguishes itself from sibling tools like list_dashboards by making clear it operates on the version history of a single dashboard, and it previews the returned fields (live status, preview URL).

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 description implies usage by describing what the output contains, but it does not explicitly say when to call this instead of list_dashboards, publish_dashboard_version, or rotate_dashboard_url. No exclusions or prerequisites are provided, leaving the agent to infer the appropriate context.

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

All tlly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources