Pingstack

Create dashboard section

create_dashboard_section

Idempotent

Add a section to a custom dashboard. Sections are the headings that organize a dashboard's checks, on the dashboard and on its status page; dashboard results list them as groups. The new section is empty and goes last. A name already used on the dashboard returns validation_failed. On a public dashboard the change shows on its status page right away. Overview can't be changed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Section heading, unique on the dashboard.
`dashboard_id`	Yes	Dashboard id (dash_…).

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`position`	Yes
`check_ids`	Yes
`dashboard_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description discloses that the section starts empty, is appended last, that duplicate names produce validation_failed, and that public dashboards propagate to the status page immediately. These are exactly the behavioral facts an agent cannot get 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.

Conciseness4/5

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

Purpose is front-loaded and each following sentence carries distinct information (semantics, ordering, error case, side effect, limitation). It is slightly dense at five sentences, and the trailing "Overview can't be changed" is terse enough to be ambiguous.

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?

An output schema exists so return values need no explanation, and the description covers ordering, empty initial state, the duplicate-name failure, and public-dashboard propagation. Only the meaning of "Overview can't be changed" is left underspecified, which is minor for a two-parameter create tool.

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% and the schema already documents both parameters, including the uniqueness constraint on name. The description restates uniqueness via the validation_failed consequence but adds no format, length, or syntax detail beyond the schema, so the baseline applies.

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 first sentence gives a specific verb and resource ("Add a section to a custom dashboard") and the second defines what a section is relative to checks and status pages. It is clearly a creation operation, implicitly distinct from update_dashboard_section, though it never names the sibling to sharpen the boundary.

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?

Usage is implied by "Add a section" and by the note that Overview can't be changed, which hints at scope limits. However, there is no explicit when-to-use vs. update_dashboard_section guidance, nor a stated prerequisite such as required permissions or dashboard editability.

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?