Skip to main content
Glama

vizier_screen_action

Read-onlyIdempotent

Screen AI agent actions before execution by checking policy, DLP, and loop constraints, then return ALLOW, REVIEW, or BLOCK with an auditable receipt.

Instructions

Screen and authorize a proposed AI agent action before execution. Evaluates deterministic policy constraints, DLP leakage, loop prevention, and returns an ALLOW / REVIEW / BLOCK decision with an auditable cryptographic receipt.

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": {
      "action_type": "<action_type>",
      "target": "<target>"
    },
    "name": "vizier_screen_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesExact target resource URI or identifier (e.g. 'mcp://github/create_issue', 'stripe://charges', 'bash://rm', 'https://api.example.com').
agent_idNoIdentifier of the agent requesting action.claude
parametersNoArguments or payload of the proposed action.
action_typeYesCategory of action: 'tool_call', 'shell_command', 'payment', 'database_write', 'external_api', 'file_modification', or 'mcp_proxy'.
principal_idNoIdentifier of the human operator or principal.operator

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description is consistent with that safety profile. The description adds meaningful behavioral context beyond annotations: deterministic policy checks, DLP leakage checks, loop prevention, and an ALLOW / REVIEW / BLOCK decision with a cryptographic receipt. It could say more about enforcement or authorization requirements, but this is strong.

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?

The description is two sentences and front-loads the core action before the behavioral details. Every clause contributes useful information with no padding.

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?

With no output schema, the description helpfully explains the return categories and the receipt. It is complete enough to invoke the tool correctly, but it does not clarify operational details such as whether it enforces the decision or how it relates to the sibling tools.

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%, so all five parameters are already documented in the input schema, including target examples and the action_type categories. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description gives a specific verb and resource: screen and authorize a proposed AI agent action before execution. It also names the evaluation dimensions and decision outputs, so the tool's function is clear. It does not explicitly differentiate itself from siblings vizier_check_policy or vizier_verify_receipt, so it falls short of 5.

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 phrase 'before execution' clearly establishes when to use the tool. However, it does not name when not to use it or point to the sibling tools as alternatives, so it lacks the explicit routing that would earn a 5.

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