Skip to main content
Glama
Sign In
SolidPing

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Manage status page section

manage_status_page_section
Destructive

Create, update, or delete status page sections to organize pinned resources; deleting a section also removes every resource pinned in it.

Instructions

Create, update or delete a section of a status page. action=create adds a section (name and slug required) and returns it. action=update edits one (sectionIdentifier required; omitted fields are kept) and returns it. action=delete permanently removes a section and every resource pinned in it, returning {deleted, identifier}. Read a page's sections with get_status_page include=sections. Annotated destructive and non-idempotent because delete is one of its actions. Every action requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.

Input Schema

NameRequiredDescriptionDefault
nameNoSection display name (required), e.g. "API services".
slugNoURL-friendly slug (required, unique within the page), e.g. "api".
actionYesWhat to do with the section.
positionNoDisplay position within the page (smaller renders earlier).
pageIdentifierYesStatus page UID or URL-friendly slug, e.g. "public".
sectionIdentifierNoStatus page section UID or URL-friendly slug, e.g. "api".

Output Schema

NameRequiredDescriptionDefault
uidNoSection UID.
nameNoSection display name.
slugNoURL-friendly slug, unique within the page.
deletedNoAlways true on success.
positionNoDisplay position (smaller renders earlier).
selectorNoDynamic membership rule; absent on hand-curated sections.
identifierNoThe identifier that was deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.42.0
    • addedInput schema / properties / action / maxLength
      Added value: +2048
    • addedInput schema / properties / action / minLength
      Added value: +1
    • addedInput schema / properties / name / maxLength
      Added value: +2048
    • addedInput schema / properties / pageIdentifier / maxLength
      Added value: +2048
    • addedInput schema / properties / pageIdentifier / minLength
      Added value: +1
    • addedInput schema / properties / sectionIdentifier / maxLength
      Added value: +2048
    • addedInput schema / properties / slug / maxLength
      Added value: +2048
  2. Changed2 schema fields changedv0.41.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / additionalProperties
      Added value: +false
  3. Addedv0.38.5

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that delete cascades to 'every resource pinned in it', that update preserves omitted fields, the return shapes per action, and the exact auth requirements (mcp scope; mcp:read tokens refused; minimum user role). This is exactly the kind of consequence and permission detail an agent cannot infer from destructiveHint alone.

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?

Front-loaded with the action enumeration, then requirements, then return values, then auth. A few phrases are redundant ('and returns it' twice) and the sentence explaining why it is annotated destructive/non-idempotent partly restates structured data, but nothing is filler.

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 mutating multi-action tool with six parameters, the description covers mode selection, conditional requirements, destructive cascade, return shape, an alternative for reads, and auth/role gating. Nothing an agent needs in order to call it safely is missing; an output schema exists so return values need no elaboration.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description adds conditional requirements the schema cannot express: name and slug are required only for create, sectionIdentifier only for update, and omitted fields are retained on update. That materially improves correct invocation.

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 set and resource ('Create, update or delete a section of a status page') and then disambiguates the three modes by action value. It also names the sibling read path (get_status_page include=sections), so the tool is distinguishable without opening the schema.

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 an explicit alternative for the read case ('Read a page's sections with get_status_page include=sections') and per-action prerequisites. It does not route the related-but-different 'pinned resources' concern to manage_status_page_resource, which a sibling tool covers, so the guidance is clear but not exhaustive.

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