Skip to main content
Glama

Show a hidden change again

unhide_change

Restores a hidden change to the user's history and recent changes so it is visible again; requires a write-scope API key.

Instructions

Show a change the user hid with hide_change in their history and recent changes again (requires a write-scope API key).

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": {
      "uuid": "<uuid>",
      "checkId": "<checkId>"
    },
    "name": "unhide_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid
checkIdYesCheck id of the hidden change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the key behavioral facts: it re-includes the change in both history and recent changes, and it requires a write-scope API key. It does not say whether the change must currently be hidden, what happens if it isn't, or what the response looks like.

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?

A single compact sentence that front-loads the effect and appends the auth requirement in parentheses. No wasted wording, though the parenthetical prerequisite could arguably be broken out for scannability.

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 simple two-parameter inverse operation with fully documented schema and no output schema, the description covers the action, its effect, and the auth prerequisite. It is slightly short of complete because it omits the error/precondition case (change not currently hidden).

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%, with uuid ("Monitor uuid") and checkId ("Check id of the hidden change") already documented in the schema. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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+resource ("Show a change the user hid ... again") and names the exact inverse operation (hide_change) plus the surfaces affected (history and recent changes). This is clearly distinguishable from siblings like get_recent_changes or hide_change.

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?

Usage is clear from the inverse relationship to hide_change: use this to restore a change the user previously hid. It also adds a prerequisite (write-scope API key). No explicit 'when not to use' or alternative restoration paths are given, keeping it below a 5.

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