Skip to main content
Glama
Sign In
SolidPing

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Manage status page resource

manage_status_page_resource
Destructive

Pin, edit, or unpin checks and check groups in status page sections to control which resources appear publicly.

Instructions

Pin, edit or unpin a resource (a check or a check group) in a status page section. action=create pins exactly one of checkUid or checkGroupUid and returns the resource. action=update edits one (resourceUid required; omitted fields are kept). action=delete unpins it, returning {deleted, identifier}; the check or group itself is untouched. Read a section's resources with get_status_page include=resources. 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
actionYesWhat to do with the resource.
checkUidNoCheck UID or slug to pin (for example api-health). Mutually exclusive with checkGroupUid; exactly one is required.
positionNoDisplay position within the section
publicNameNoDisplay name for the public page (defaults to the check or group name)
explanationNoShort explanation rendered under the resource
resourceUidNoStatus page resource UID (get_status_page include=resources lists them).
checkGroupUidNoCheck group UID or slug to pin as one aggregated component. Mutually exclusive with checkUid; exactly one is required.
pageIdentifierYesStatus page UID or URL-friendly slug, e.g. "public".
sectionIdentifierYesStatus page section UID or URL-friendly slug, e.g. "api".

Output Schema

NameRequiredDescriptionDefault
uidNoResource UID.
deletedNoAlways true on success.
checkUidNoPinned check UID, when the resource targets a check.
positionNoDisplay position within the section (smaller renders earlier).
identifierNoThe identifier that was deleted.
publicNameNoDisplay name shown on the public page.
explanationNoShort explanation rendered under the resource.
checkGroupUidNoPinned check group UID, when the resource targets a group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.42.0
    • addedInput schema / properties / action / maxLength
      Added value: +2048
    • addedInput schema / properties / action / minLength
      Added value: +1
    • addedInput schema / properties / checkGroupUid / maxLength
      Added value: +2048
    • addedInput schema / properties / checkUid / maxLength
      Added value: +2048
    • addedInput schema / properties / explanation / maxLength
      Added value: +2048
    • addedInput schema / properties / pageIdentifier / maxLength
      Added value: +2048
    • addedInput schema / properties / pageIdentifier / minLength
      Added value: +1
    • addedInput schema / properties / publicName / maxLength
      Added value: +2048
    • addedInput schema / properties / resourceUid / maxLength
      Added value: +2048
    • addedInput schema / properties / sectionIdentifier / maxLength
      Added value: +2048
    • addedInput schema / properties / sectionIdentifier / minLength
      Added value: +1
  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
Behavior4/5

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

Adds real context beyond annotations: it explains why destructive/non-idempotent applies (delete is one of its actions), guarantees the underlying check/group is untouched, states the return shape for delete, and documents the mcp scope plus user-role requirement. The remaining gap is minor since annotations already carry the safety profile.

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-loads the verb set and the three action branches in tight sentences; the trailing auth/scope sentence is useful but slightly dense, and the return-shape detail partially duplicates the output schema.

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 nine-parameter, three-mode mutation tool this covers the decisions an agent must make: which branch to invoke, which identifiers each branch needs, side effects, permissions, and where to read the current state.

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 coverage is 100%, so the baseline is 3; the description goes further by stating action-conditional requirements (resourceUid only for update, checkUid/checkGroupUid mutual exclusivity for create) and partial-update semantics that the schema itself does not encode.

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?

Names a concrete resource (a check or check group pinned in a status page section) and enumerates the three operations with their distinct semantics, so it is clearly separable from sibling tools like manage_status_page_section and get_status_page.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit per-action conditions (create pins exactly one of checkUid/checkGroupUid; update requires resourceUid and keeps omitted fields; delete unpins) and routes the agent to get_status_page include=resources for reading instead.

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