Skip to main content
Glama

IntentFence Agent Action Firewall

by io.github.razel369

IntentFence Agent Checkout

intentfence_checkout
Read-onlyIdempotent

Free machine checkout builder. Select a paid IntentFence outcome and receive the exact endpoint, validated request, USDC cap, shell-safe Agentic Wallet argv, MCP tool call, and opt-in local auto-payment budget. It never signs or initiates payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoThe exact product input. Omit only to receive a non-executable example recipe.
productYesThe paid outcome the agent wants to buy.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds that it never signs or initiates payment and lists outputs, aligning with and enhancing annotation context.

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 concise sentences, front-loaded with key outputs and a clarifying behavioral note. No redundancy.

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?

Covers purpose, outputs, and safety. With no output schema, could specify return format more, but still adequate for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description explains 'select a paid outcome' for product and notes omitting input yields an example recipe, adding meaning beyond schema.

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 specifies the tool as a 'Free machine checkout builder' that selects a paid outcome and returns endpoint, request, etc. It clearly distinguishes from sibling product-specific tools.

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?

States to 'Select a paid IntentFence outcome' and clarifies it never signs or initiates payment, implying use for preparing checkout. Does not explicitly mention alternatives or when not to use.

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

All IntentFence Agent Action Firewall toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, from risk scanning to authorization, preflight checks, and specific data retrieval. Descriptions are detailed and non-overlapping.

Naming Consistency5/5

All tools follow a consistent 'intentfence_<descriptive_name>' pattern with snake_case, making them predictable and easy to distinguish.

Tool Count5/5

10 tools is well-scoped for a security firewall server, covering a range of free and paid services without being overwhelming or too sparse.

Completeness3/5

The set covers assessment, authorization, and data retrieval, but lacks tools for managing the firewall configuration itself (e.g., allowlist CRUD), leaving some gaps in lifecycle coverage.

Resources