Skip to main content
Glama
emiliaprotocol

emilia-mcp-server

Official

ep_guard_action

Submit an action for policy evaluation and human authorization before irreversible operations. Returns APPROVED to proceed or BLOCKED with signoff details.

Instructions

REQUIRED before any irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. Returns APPROVED with a receipt the action may proceed under, or BLOCKED with a receipt_id + signoff_id while a named human reviews. Do NOT execute the action without an APPROVED result — if BLOCKED, poll ep_check_signoff with the receipt_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesThe organization this action belongs to.
action_typeYesKind of action, e.g. "large_payment_release", "vendor_bank_account_change", "ai_agent_payment_action".
target_resource_idYesWhat is being acted on — an invoice id, account id, or record id.
amountNoAmount, for payments/releases.
currencyNoISO currency code, e.g. "USD".
destinationNoWhere funds or data are going (account, address).
summaryNoOne-line, human-readable description the approver will see.
risk_flagsNoOptional risk signals, e.g. ["new_destination","after_hours"].
Behavior4/5

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

The description discloses that the tool returns either 'APPROVED' or 'BLOCKED' and involves human authorization. Annotations already indicate readOnlyHint=false, so the description adds value by detailing the workflow and the need for polling. It could mention idempotency or side effects but is strong overall.

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 dense paragraph that front-loads the core purpose. It is efficient with no wasted words, though a bit more structure (e.g., bullet points) could improve readability.

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?

Given the tool's complexity (8 parameters, security-critical role, no output schema), the description adequately covers the workflow (submission, approval/blocked, polling). It does not cover error handling or rate limits but is sufficient for an AI agent.

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% with descriptions for all 8 parameters. The tool description adds context (e.g., examples for action_type, summary as human-readable) but does not significantly expand on parameter meaning beyond the schema. Baseline 3 is appropriate.

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 as a required guard before irreversible actions, listing specific examples like payments, deletions, and account changes. It distinguishes itself from sibling tools by describing the approval/blocked result and referencing ep_check_signoff for polling.

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 the tool is required (before any irreversible action) and warns against executing the action without an approved result. It also provides clear guidance on what to do if blocked (poll ep_check_signoff).

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/emiliaprotocol/emilia-protocol'

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