Skip to main content
Glama

BLACK_WALL pre-action risk check

forecast

Assess risk before taking irreversible actions like sending emails, making payments, or deleting files. Returns a risk score and a GO, CAUTION, or STOP recommendation to prevent costly mistakes.

Instructions

Call this BEFORE taking ANY irreversible or high-stakes action — sending an email, making a payment, running SQL, deleting files or data, posting public content, calling an external API that changes state. It returns a risk score (0–100), a recommendation (GO / CAUTION / STOP), and named red flags. If the recommendation is STOP, do not take the action — surface the flags to the user instead. If CAUTION, confirm with the user first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action about to be taken, e.g. 'send_email', 'make_payment', 'run_sql', 'delete_file', 'delete_database', 'post_content', 'api_call'.
inputsYesThe concrete parameters of the action: recipient, amount_usd, SQL statement, file path, message body, URL, etc. Include everything relevant to judging risk.
contextNoOptional situational context: { agent_role, user_intent, environment } — helps the model judge whether the action fits the intent.
depthNoAnalysis depth. 'standard' (default) or 'deep' (more thorough, costs more).
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the return values but does not explicitly state that the tool is read-only or non-destructive. While the name 'forecast' implies safety, the description could be clearer about its lack of side effects.

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?

The description is a single paragraph that is well-structured and front-loaded with the main directive. It is slightly verbose but contains essential guidance; minor conciseness improvements could be made.

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?

The description covers all necessary aspects: when to use, what parameters are for, what output to expect, and how to handle results. Given no output schema, it adequately describes the return structure and action protocol.

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 baseline is 3. The description does not add significant meaning beyond what the schema already provides for each parameter; it gives examples in the overview but not per-parameter elaboration.

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?

The description clearly states the tool's purpose: a pre-action risk check to be called before irreversible or high-stakes actions. It lists specific examples and explains the output, making it distinct and clear.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool ('BEFORE taking ANY irreversible or high-stakes action') and provides actionable guidance on how to interpret the recommendation (STOP, CAUTION, GO). This is comprehensive and leaves no ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bluetieroperations-create/blackwall-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server