Skip to main content
Glama
Sign In

tlly

by dev.tlly
OverviewDiscussionsAdmin

Rotate dashboard URL

rotate_dashboard_url
Destructive

Give a dashboard a new public URL and disable the old one at once (e.g. if a link leaked). Spec and data are unchanged.

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

Input Schema

NameRequiredDescriptionDefault
dashboard_idYesid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's real contribution is the consequence: the old URL is disabled at once and spec/data are untouched. That tells the agent precisely what breaks and what is preserved, though it omits permissions and whether the old URL can be restored.

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?

Two short sentences, zero filler, with the action and the immediate effect leading. The 'unchanged' caveat is placed last where it belongs.

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 single-parameter destructive operation with annotations covering safety and no output schema, the description supplies the key facts: what gets replaced, that the old link dies, and that dashboard content is unaffected. Only reversibility and auth requirements are left unspecified.

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?

Only one parameter and schema coverage is 100%, so the schema technically documents it (albeit tersely as 'id'). The description implies the target is a dashboard but adds no format or lookup guidance beyond that, so baseline 3 applies.

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: gives a dashboard a new public URL and disables the old one. The clause 'Spec and data are unchanged' cleanly separates it from update_dashboard and delete_dashboard in the sibling list.

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 parenthetical '(e.g. if a link leaked)' gives a concrete triggering condition, which is more than most descriptions offer. It stops short of naming alternatives like update_dashboard or stating when not to rotate (e.g. when the URL is referenced elsewhere).

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