Skip to main content
Glama

upsert_guardrail_mcp_server

DestructiveIdempotent

Create or replace a guardrail-to-MCP-server mapping while preserving mappings for other servers; optionally set input/output run phases, defaulting to both.

Instructions

Create or replace one guardrail mapping for one MCP server without changing mappings for other servers. Requires a guardrail with target mcp_tools. run_on defaults to both input and output. Use list_guardrail_mcp_servers to inspect the current mapping set first. Repeating the same mapping 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_server_id": "<mcp_server_id>"
    },
    "name": "upsert_guardrail_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_onNoGuardrail phases to run for this MCP server
guardrail_idYesGuardrail UUID or slug
mcp_server_idYesMCP server UUID
mcp_integration_capability_idsNoMCP integration capability UUIDs covered by this mapping

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.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds value beyond them with the mcp_tools guardrail prerequisite and the scoping guarantee that other servers' mappings are untouched. It stops short of saying whether an existing mapping's run_on and capability list are fully overwritten or merged, which matters for a destructive upsert.

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, resource, and scope, then adds prerequisites and the inspection hint in short, ordered sentences. The run_on default sentence largely duplicates the schema default, a small redundancy in an otherwise lean definition.

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?

An output schema exists, so return values need no explanation; the description instead covers scope, prerequisites, idempotency, and a discovery alternative, which is the right material for a 4-parameter mutation tool. The one meaningful omission is replacement semantics for mcp_integration_capability_ids on an existing mapping.

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 every parameter carries a description, including run_on with its default, so the schema already does the work. The description only restates the run_on default and adds a guardrail-type precondition, adding little semantic detail beyond the structured fields. 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 pair ('Create or replace') plus the precise resource ('one guardrail mapping for one MCP server') and the scope boundary ('without changing mappings for other servers'). That scope clause also implicitly separates it from the bulk sibling replace_guardrail_mcp_servers, so an agent can choose without opening 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 a concrete pre-call step ('Use list_guardrail_mcp_servers to inspect the current mapping set first') and a hard precondition ('Requires a guardrail with target mcp_tools'). It does not explicitly name when to prefer the bulk replace_guardrail_mcp_servers variant, though the 'one server' scope makes that inference easy.

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