Skip to main content
Glama
Sign In
agent-pay-gate

agent-pay-gate

by NariP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Create a quote

create_quote

Build an order and lock a fixed, no-charge quote; any change requires a new quote, and orders exceeding merchant agent limits are refused.

Instructions

Build an order and get a fixed quote. This charges nothing. The total is locked to this quote; to change anything, create a new quote. Orders over the merchant's limits for agents are refused here.

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": {
      "items": "<items>",
      "intent": "<intent>"
    },
    "name": "create_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
intentYesThe user's request in their own words. Shown to the human on the approval page so they can spot a wrong order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well by stating that it charges nothing, that the total is locked, that changes require a new quote, and that over-limit orders are refused. It still omits operational details such as required permissions, whether an approval step is involved, or quote expiry/idempotency behavior.

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?

The description is four short sentences, front-loads the core action, and every sentence adds a distinct constraint: no charge, total lock, change policy, and limit refusal. There is no filler or redundant wording.

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?

For a quote-creation tool with no annotations and no output schema, the description gives the essential behavioral context: cost-free, immutable total, new quote for changes, and limit enforcement. It is still somewhat incomplete about parameters and about what is returned or how approval works, but the core call context is present.

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

Parameters2/5

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

Schema description coverage is only 50%: the intent parameter is documented in the schema, but the items array and its nested sku/quantity fields are not described anywhere. The description says 'Build an order' but adds no meaning about item structure, quantity bounds, or what intent is for, so it does not compensate for the coverage gap.

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 description states a specific verb and resource: 'Build an order and get a fixed quote.' It also clarifies the key scope that this is a non-charging, locked quote, which helps distinguish it from payment actions. It does not explicitly differentiate itself from sibling tools like check_payment or request_payment.

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

Usage Guidelines3/5

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

Usage is implied: create a quote to lock a total before payment, and create a new quote to change anything. The description also notes that orders over merchant limits are refused. However, it gives no explicit when-to-use versus alternatives guidance or prerequisites such as approval flow.

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

Deploy Server

Other Tools