Skip to main content
Glama

SpendPreflight: pricing, defaults, how to pay

get_service_info
Read-onlyIdempotent

Use when you need more tools: browse Buyers, Sellers, Books and Data APIs, prices, rules and examples. If you have a payment challenge, call preflight_payment directly. Free, read-only service reference. Use when you need prices, default spending rules, payment setup, trial allowance, or a ready-to-use example call. If you already have a payment challenge or cart, call preflight_payment directly; this reference call is optional. Takes no arguments and performs no payee screening or payment decision. Use check_payee for standalone payee risk; use preflight_payment for an x402 challenge or cart and an allow/hold/block decision.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_service_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
siteYes
trustYes
paymentYes
pricingYes
examplesYes
http_apiYes
disclaimerYes
guaranteesYes
tool_groupsYes
when_to_useYes
client_guardYes
example_callYes
example_noteYes
default_rulesYes
guidance_versionYes
identity_bindingYes
recommended_toolsYes
free_trial_per_dayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / identity_binding
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "recommended_tools",
      -  "tool_groups",
      -  "examples",
      -  "guidance_version",
      -  "example_call",
      -  "example_note",
      -  "when_to_use",
      -  "pricing",
      -  "free_trial_per_day",
      -  "payment",
      -  "default_rules",
      -  "http_api",
      -  "client_guard",
      -  "site",
      -  "guarantees",
      -  "trust",
      -  "disclaimer"
      -]New value: +[
      +  "identity_binding",
      +  "recommended_tools",
      +  "tool_groups",
      +  "examples",
      +  "guidance_version",
      +  "example_call",
      +  "example_note",
      +  "when_to_use",
      +  "pricing",
      +  "free_trial_per_day",
      +  "payment",
      +  "default_rules",
      +  "http_api",
      +  "client_guard",
      +  "site",
      +  "guarantees",
      +  "trust",
      +  "disclaimer"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / examples
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / recommended_tools
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / tool_groups
      Added value: +{
      +  "additionalProperties": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "guidance_version",
      -  "example_call",
      -  "example_note",
      -  "when_to_use",
      -  "pricing",
      -  "free_trial_per_day",
      -  "payment",
      -  "default_rules",
      -  "http_api",
      -  "client_guard",
      -  "site",
      -  "guarantees",
      -  "trust",
      -  "disclaimer"
      -]New value: +[
      +  "recommended_tools",
      +  "tool_groups",
      +  "examples",
      +  "guidance_version",
      +  "example_call",
      +  "example_note",
      +  "when_to_use",
      +  "pricing",
      +  "free_trial_per_day",
      +  "payment",
      +  "default_rules",
      +  "http_api",
      +  "client_guard",
      +  "site",
      +  "guarantees",
      +  "trust",
      +  "disclaimer"
      +]
  3. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / description
      Added value: +"Example arguments: {}"
    • addedOutput schema / properties / example_call
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / example_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / guidance_version
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "when_to_use",
      -  "pricing",
      -  "free_trial_per_day",
      -  "payment",
      -  "default_rules",
      -  "http_api",
      -  "client_guard",
      -  "site",
      -  "guarantees",
      -  "trust",
      -  "disclaimer"
      -]New value: +[
      +  "guidance_version",
      +  "example_call",
      +  "example_note",
      +  "when_to_use",
      +  "pricing",
      +  "free_trial_per_day",
      +  "payment",
      +  "default_rules",
      +  "http_api",
      +  "client_guard",
      +  "site",
      +  "guarantees",
      +  "trust",
      +  "disclaimer"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses that the call is free, takes no arguments, and performs no payee screening or payment decision — useful negative scope. It loses a point only because the payment-challenge caveat is stated twice rather than adding further behavioral detail (e.g. what the reference payload contains).

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?

Key routing information is front-loaded, but the guidance is redundant: the instruction to call preflight_payment directly when holding a challenge/cart appears twice in near-identical form, and the opening 'use when you need more tools' is vague filler. Tightening would make it noticeably stronger.

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?

An output schema exists, so return values need not be explained, and the description fully covers invocation conditions, cost, argument count and exclusions. Nothing an agent needs to call this correctly is missing.

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?

With zero parameters the schema carries no semantic load, so there is nothing to compensate for; the description correctly notes it takes no arguments. Baseline 4 applies for a parameterless tool.

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 states a specific resource set — Buyers, Sellers, Books and Data APIs, plus prices, rules and examples — and frames it as a free, read-only reference call taking no arguments. This is clearly distinguishable from mutating or decision-making siblings like preflight_payment and check_payee.

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?

It gives explicit routing: use this when you need prices, default spending rules, payment setup, trial allowance or example calls; use preflight_payment directly if you already hold a challenge or cart; use check_payee for standalone payee risk. Both when-to-use and when-not-to-use are named with the alternative tools.

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.