Skip to main content
Glama

Boundra — Payment Approval Gateway for AI Agents

render_template

Read-onlyIdempotent

Render a natural-language rule from a template + parameters (then compile, sign & publish)

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": {
      "template_id": "<template_id>",
      "whitelist": "<whitelist>"
    },
    "name": "render_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyNoOptional total daily spending cap override
per_txNoOptional per-transaction spending cap override
ask_aboveNoOptional amount above which human approval is required
whitelistYesApproved recipient hosts, addresses or identifiers
template_idYesIdentifier returned by list_templates

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / ask_above / description
      Added value: +"Optional amount above which human approval is required"
    • addedInput schema / properties / daily / description
      Added value: +"Optional total daily spending cap override"
    • addedInput schema / properties / per_tx / description
      Added value: +"Optional per-transaction spending cap override"
    • addedInput schema / properties / template_id / description
      Added value: +"Identifier returned by list_templates"
    • addedInput schema / properties / whitelist / description
      Added value: +"Approved recipient hosts, addresses or identifiers"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is already covered and the description need only add context. Instead it introduces tension: 'compile, sign & publish' names state-changing operations that the annotations say this tool does not perform, leaving the agent unsure whether a call merely renders text or actually publishes a rule. The description also says nothing about validation failures, e.g. what happens with an unknown template_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence is appropriately sized for this tool. However, the parenthetical is not just filler, it is the least clear part of the definition and the part most likely to be misread, so brevity does not translate into precision here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full input schema, rich annotations and an output schema, much of the burden is already carried by structured fields. Still missing is the workflow position: whether rendering is a terminal read step or must be followed by another tool to compile, sign and publish, which an agent needs in order to plan a multi-step policy change.

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% and each optional cap override (daily, per_tx, ask_above) and whitelist is already documented in the schema. The description adds no meaning beyond 'template + parameters', so it neither compensates nor detracts; the baseline of 3 applies.

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 main clause gives a specific verb and resource: 'Render a natural-language rule from a template + parameters'. That is far more informative than the name alone. The trailing parenthetical '(then compile, sign & publish)' blurs the boundary of what this tool itself does versus what happens downstream, and no sibling (list_templates, set_policy) is named for contrast.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only routing hint, that template_id comes from list_templates, lives in the schema rather than the description. An agent must infer on its own whether to call this before or instead of set_policy or request_policy_change.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.