Pingstack

Reorder dashboard checks

reorder_dashboard_checks

DestructiveIdempotent

Set the display order of the checks in one section of a custom dashboard, or of its checks outside any section when group_id is omitted. check_ids must list every check in that section exactly once, first to last; a missing, extra or repeated id returns invalid_arguments and nothing changes. Checks stay in their sections, and public dashboards and Overview can't be reordered. Returns the dashboard id and the new order.

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>",
      "check_ids": "<check_ids>"
    },
    "name": "reorder_dashboard_checks"
  }
}

Input Schema

Name	Required	Description
`group_id`	No	Section to reorder, by the id the dashboard's sections list reports. Omit for checks not in a section.
`check_ids`	Yes	Every check id in the group, each once, in the new order.
`dashboard_id`	Yes	Dashboard id (dash_…).

Output Schema

Name	Required	Description	Default
`id`	Yes
`check_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / group_id / description

Previous value: -"Group to reorder, by the group id the dashboard lists. Omit for checks not in a group."New value: +"Section to reorder, by the id the dashboard's sections list reports. Omit for checks not in a section."

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description justifies both: the call replaces the full ordering atomically ('nothing changes' on validation failure) and checks stay confined to their sections. It also discloses two hard capability limits (public dashboards, Overview) and the failure mode (invalid_arguments) that an agent cannot infer from structured fields.

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?

Three tightly packed sentences: operation and scope first, then the validation contract and failure behavior, then the return value. Every clause carries a constraint an agent needs; nothing is redundant.

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

Completeness5/5

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

For a 3-parameter mutation with an output schema, the description covers scope, atomic validation, ordering constraints, capability exclusions, and the returned payload. Nothing material to a correct invocation is left to inference.

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 both parameters are already documented, including that check_ids must contain each id once and that group_id should be omitted for unsectioned checks. The description reinforces the completeness/permutation rule and ties it to the invalid_arguments failure, which is modest added meaning rather than new syntax or format detail.

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 ('Set the display order of the checks') and scopes it precisely to one section of a custom dashboard, or to unsectioned checks when group_id is omitted. No sibling in the catalog performs reordering, and the definition makes that scope unambiguous without requiring the schema to be opened.

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?

Gives explicit preconditions (check_ids must be a complete permutation of the section) and explicit exclusions (public dashboards and Overview can't be reordered), plus the group_id-omitted case. It does not name an alternative tool, but no sibling appears to cover this operation, so the guidance is effectively complete.

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

All Pingstack tools Inspect

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

Need Help?