Skip to main content
Glama
Sign In

GovGazette

by io.github.mooshee
OverviewDiscussionsAdmin

Replace a saved search feed link

rotate_saved_search_feed
Destructive

Replace the private feed link for one saved search owned by the authenticated workspace, immediately revoking its previous link. Requires explicit user intent. Does not delete the search or its events. Keep the replacement link private; a lost response may mean the link changed and cannot be recovered by listing searches.

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": {
      "id": "<id>"
    },
    "name": "rotate_saved_search_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSaved search UUID returned by create_saved_search or list_saved_searches, owned by this workspace.

Output Schema

NameRequiredDescriptionDefault
feed_pathYesReplacement private capability path; the previous link is revoked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: states the previous link is immediately revoked, that the search and events survive, and warns that a lost response may mean an irrecoverable change not recoverable via listing. This is exactly the destructive/irreversible context an agent needs beyond destructiveHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight sentences, front-loaded with the action, followed by the precondition and the irreversible-loss warning. No filler; each sentence carries a distinct operational fact.

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?

With an output schema present, return values need not be explained, and the description covers the key risks of an irreversible, non-idempotent mutation plus the ownership precondition. Nothing an agent needs to invoke it safely is missing.

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 id parameter is fully documented in the schema as a UUID from create_saved_search or list_saved_searches. The description adds only the ownership constraint, so 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 (replace/rotate) and resource (private feed link for a saved search) with explicit scope (one saved search, authenticated workspace). It is clearly distinguishable from siblings like delete_saved_search or list_saved_searches.

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?

"Requires explicit user intent" gives a clear precondition for use, and "Does not delete the search or its events" implicitly steers agents away from the delete siblings. It stops short of naming an alternative tool or a when-not-to-use case explicitly.

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

All GovGazette toolsInspect
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