Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change a monitor's request headers

vs_monitors_update_request_headers
DestructiveIdempotent

Replace the request headers a monitor's check sends. Headers that carry sign-in details are entered in the dashboard; a saved one is kept.

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": "vs_monitors_update_request_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor id.
headersNoRequest headers to send, as { "Header-Name": "value" }. The list replaces the current one. Headers that carry sign-in details are entered in the dashboard: a saved one shows as "__vs_secret__", and it is kept whether you send it back with that value or leave it out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it is a wholesale replacement rather than a merge, and secret-bearing headers are preserved as "__vs_secret__" whether echoed back or omitted.

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?

Two short sentences with the core replacement semantics front-loaded and the secret caveat second. Nothing is wasted.

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 destructive, idempotent mutation with a fully documented two-parameter schema and no output schema, the description covers the two things the schema alone would not surface: replacement-not-merge and secret retention. The one gap is what happens if the optional headers object is omitted entirely (no-op vs. clear all), which remains undefined.

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% and the headers property description already spells out the replacement rule and the "__vs_secret__" placeholder, so the description largely restates structured data. Baseline 3 applies; it adds no syntax or format detail the schema lacks.

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 and resource with scope: "Replace the request headers a monitor's check sends." That cleanly separates it from siblings such as vs_monitors_update_request_body, vs_monitors_update_check_method, and vs_monitors_update_expectations without the agent opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb "Replace" and the field name, but the description never states preconditions, when to prefer this over other update_* siblings, or how it interacts with the dashboard-only header entry. No explicit when/when-not guidance.

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

All Visual Sentinel 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