GateCheck by LarryBuildsAI

Boundary Guard Check

boundary_guard_check

Read-onlyIdempotent

Create a deterministic, read-only pre-action receipt from request, policy, and optional result evidence. Use before an agent posts, spends, lists, or writes so the decision can be audited; no external action is executed.

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": {
      "request": "<request>"
    },
    "name": "boundary_guard_check"
  }
}

Input Schema

Name	Required	Description
`policy`	No	Decision object, e.g. allow/retry/review/block and reason.
`result`	No	Optional result or dry-run summary to hash into evidence.
`request`	Yes	Action metadata the agent is about to perform.
`nextStep`	No	Optional guidance stored in the receipt.

Output Schema

Name	Required	Description	Default
`decision`	Yes
`nextStep`	No
`createdAt`	Yes
`receiptId`	Yes
`evidenceHash`	Yes
`claimBoundary`	Yes
`marketplacePositioning`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, not destructive, so the bar is lower. The description adds useful context: 'deterministic,' 'pre-action receipt,' and 'no external action is executed,' which clarifies the tool's side-effect-free and audit-focused behavior. It does not contradict annotations and adds value beyond them.

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 sentences with no fluff. The first sentence states purpose and inputs; the second gives usage timing and reassurance about safety. Every word earns its place and the key information is front-loaded.

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?

Given the presence of an output schema, full schema coverage, and robust annotations, the description is complete enough. It explains what the tool does, when to use it, what inputs are expected, and that no external action occurs. No critical gaps remain for an agent to use it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes slightly beyond by enumerating the core inputs ('request, policy, and optional result evidence'), which maps to three of the four parameters and helps the agent understand their roles. It omits 'nextStep' but the schema covers that.

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 uses a specific verb+resource: 'Create a deterministic, read-only pre-action receipt' and clearly scopes it to 'from request, policy, and optional result evidence.' It distinguishes itself from sibling tools by emphasizing it is a pre-action audit receipt with no external action, which separates it from launch packs and resource probes.

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?

It explicitly states when to use: 'Use before an agent posts, spends, lists, or writes so the decision can be audited.' It also clarifies a key exclusion ('no external action is executed'). However, it does not explicitly name alternative tools or when not to use it, so it stops short of a 5.

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

All GateCheck by LarryBuildsAI tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.