Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Report a problem to Visual Sentinel

vs_feedback_report

Send the Visual Sentinel team a report about a false alert, a bug or a missing feature, optionally for one monitor or incident.

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": {
      "type": "<type>",
      "note": "<note>"
    },
    "name": "vs_feedback_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesWhat happened or what is missing, in a few sentences (up to 1000 characters).
typeYesfalse_positive (an alert or incident that was wrong), bug, or missing_feature.
monitorIdNoOptional: the monitor the report is about.
incidentIdNoOptional: the incident the report is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the agent knows this writes new data non-destructively and is non-idempotent. The description adds that the payload leaves for a human team and that monitor/incident association is optional, which is useful. It says nothing about what submission returns, whether a ticket ID is produced, or rate limits.

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?

A single sentence that front-loads the action and audience, then qualifies the target resources. Nothing is redundant with the title or schema and 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 low-complexity, no-output-schema submission tool with fully documented parameters and annotations, the description supplies everything needed to call it correctly. Only the post-submission outcome (confirmation, ticket reference) is unaddressed, which is minor.

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%, with the type enum and note length spelled out in the schema, so the schema carries the semantic load. The description's only added nuance is that monitorId/incidentId are optional and singular ('for one monitor or incident'). Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: send a report to the Visual Sentinel team covering false alerts, bugs, or missing features. An agent immediately understands this is a feedback channel, not a monitoring action, so it is not confusable with any sibling. It stops short of an explicit 'use this instead of X' distinction, but no sibling overlaps functionally.

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?

The description enumerates the three legitimate report categories (false alert, bug, missing feature) and notes that monitor/incident scoping is optional, giving clear context for invocation. It gives no exclusions (e.g., don't use for support billing issues) and no statement about when this should be preferred over directly fixing a monitor.

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