Skip to main content
Glama
Signal Feed API: market regime for agents

Signal Feed API: market regime for agents

get_payment_offer

Preview today's x402 payment offer without paying: see the price, network, asset, payee, and whether the paid tool is configured in this server.

Instructions

Free. Use before paying to see exactly what would be charged: today's x402 offer (price, network, asset, payee) without paying, and whether the paid tool is configured in this server.

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_payment_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: the call is free and returns offer details "without paying," i.e. no charge and no side-effecting transaction. It says nothing about authentication, rate limits, or what is returned when the paid tool is not configured, so the disclosure is partial rather than complete.

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

Conciseness4/5

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

A single compact sentence with the cost caveat ("Free.") front-loaded and the value proposition immediately after. The parenthetical field list is dense but earns its place by telling the agent what it will learn before paying.

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?

An output schema exists, so return values need no explanation, and the description covers cost, timing relative to payment, and the configuration check. The one gap is behavior in the unconfigured/error case, which matters for a pre-payment gate but is minor given the output schema.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly adds no parameter guidance and instead spends its words on the returned offer fields.

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?

Names a specific resource (today's x402 payment offer) and enumerates the exact fields returned: price, network, asset, payee. It also states the second purpose — checking whether the paid tool is configured in this server — which no sibling tool (get_catalog, get_schema, list_issues, etc.) covers, so the agent can distinguish it immediately.

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?

"Use before paying" gives an explicit trigger condition that an agent can act on, effectively ruling out this tool once payment has occurred. There is no explicit statement of when not to use it or a named alternative, which keeps it below a 5.

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