Skip to main content
Glama

replace_guardrail_mcp_servers

DestructiveIdempotent

Replaces the complete MCP-server mapping set for a guardrail, removing any servers omitted from the new map or clearing all mappings with an empty object. Review current mappings first.

Instructions

Replace the complete MCP-server mapping set for one guardrail. Requires a guardrail with target mcp_tools. Any existing server omitted from mcp_servers is removed, and an empty object clears all mappings. Read list_guardrail_mcp_servers first. Repeating the same complete map is safe.

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": {
      "guardrail_id": "<guardrail_id>",
      "mcp_servers": "<mcp_servers>"
    },
    "name": "replace_guardrail_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
mcp_serversYesComplete MCP-server mapping set keyed by server UUID; an empty object clears every mapping
guardrail_idYesGuardrail UUID or slug

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv0.12.2

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by stating the destructive closure rule ("Any existing server omitted from mcp_servers is removed") and the clear-all case ("an empty object clears all mappings"). The line "Repeating the same complete map is safe" explicitly corroborates idempotentHint, and the mcp_tools prerequisite is operational context the annotations cannot convey.

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?

Four short sentences, front-loaded with the action and its destructive scope, then the prerequisite, then the read-first advice. Nothing is padded and no sentence restates the tool name or the 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?

An output schema exists, so return values need no explanation, and the annotations already flag destructiveHint and idempotentHint. For a two-parameter replacement tool the description covers scope, prerequisite, data loss, and ordering advice without gaps.

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, but the description adds real meaning by framing mcp_servers as a complete replacement set whose omissions are deletions rather than as a partial patch. It leaves run_on and mcp_integration_capability_ids to the schema, which describes them adequately.

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?

Specific verb plus resource plus scope: "Replace the complete MCP-server mapping set for one guardrail." The word "complete" and the closure rule distinguish it from the sibling upsert_guardrail_mcp_server, which touches one server, without the agent needing to open either 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 prerequisite ("Requires a guardrail with target mcp_tools") and an explicit read-first step ("Read list_guardrail_mcp_servers first"). What it does not do is name upsert_guardrail_mcp_server as the alternative for single-server edits, so an agent that only wants to change one mapping must infer the routing itself.

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