Monitor Hub

update_status_page

Updates public status page configuration and slug for the user workspace.

Use this tool when a user wants to rename or update their public status page URL.

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": {
      "slug": "<slug>"
    },
    "name": "update_status_page"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Purpose: New unique URL slug for the status page. Example values: my-company-status startup-uptime Validation rules: Must be URL-safe (no spaces or special characters).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already disclose that this is a non-destructive, closed-world mutation, so the description's added burden is lower. It contributes the useful fact that the target is a PUBLIC page scoped to the user workspace, but it omits the operationally important question of what happens to the previous URL (redirect vs. broken link) and any permission requirements for changing a public-facing address.

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?

Two short sentences, front-loaded with the action and followed by the selection cue, with no filler. The mild redundancy between "configuration" in the first sentence and "rename the URL" in the second is the only noise.

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 single-required-parameter mutation with annotations covering the safety profile and no output schema, the definition supplies what is needed to invoke it correctly. The remaining gap is downstream effect disclosure about the old public slug, which is worth having but not essential to calling the 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 description coverage is 100%, and the single slug parameter is already documented with purpose, example values, and URL-safety validation rules. The description only gestures at it via "slug" and "public status page URL", adding no format or uniqueness constraints beyond the schema, so the baseline of 3 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 description states a specific verb and resource ("Updates public status page configuration and slug for the user workspace") and the second sentence narrows this to renaming the public status page URL. It is clear at a glance, though the word "configuration" overreaches the single slug parameter the schema actually accepts, so the scope is slightly broader than the tool's real capability.

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?

The second sentence gives an explicit trigger condition: use when a user wants to rename or update their public status page URL. No exclusion or alternative tool is named, so the agent gets clear positive guidance but no rule for choosing between this and status-page listing or other update tools.

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

All Monitor Hub 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?