Skip to main content
Glama

get_dashboard_migration_status

Read-only

Tracks progress of migrating legacy Core UI Performance Analytics dashboards to Platform Analytics, showing readiness, logs, migrated items, and dashboards without a new version.

Instructions

Progress of the move from Core UI (legacy) Performance Analytics dashboards to Platform Analytics: legacy dashboards by migration readiness, Migration Center logs (par_coreui_migration_bridge_*), migrated dashboards and widgets, and legacy dashboards with no Platform Analytics version yet. Read-only

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax dashboards to list in each section (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the trailing 'Read-only' adds nothing new. What the description does add is meaningful: it names the underlying log table pattern (par_coreui_migration_bridge_*) and the specific categories of data that will be returned, which helps an agent interpret results on a tool without an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence establishes the domain, then a compact colon-list enumerates sections; no filler. It is slightly dense as a single run-on, but every clause conveys distinct reported content rather than repeating the name.

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, no-required-parameter status tool with no output schema, describing the four returned sections is exactly the missing information an agent needs. The only real gap is the absence of guidance on when this should be preferred over neighboring dashboard/status tools.

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?

There is a single optional parameter with 100% schema description coverage, including its default of 25 and its per-section scope. The description adds no further detail about how limit applies, so the schema carries the load and baseline 3 is appropriate.

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 names a specific subject (progress of the Core UI / Performance Analytics to Platform Analytics dashboard migration) and enumerates the four sections it reports: legacy dashboards by readiness, Migration Center logs, migrated dashboards/widgets, and unmigrated legacy dashboards. It is clearly distinct from generic dashboard readers like get_pa_dashboard, though it never states that contrast explicitly.

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 explicit when-to-use, when-not-to-use, or alternative routing. An agent could infer this is for checking migration progress, but nothing tells it whether to call this versus get_pa_dashboard or sync_status, or whether prerequisites exist before a migration run.

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

Deploy Server

Other Tools