Skip to main content
Glama

Quote a service call

quote_service
Read-only

Price ONE call to a catalog service WITHOUT paying it: it charges nothing, signs nothing and reserves no budget. Pass exactly what you would pass to pay_service (the same slug, path, method, search, headers, body and delegationId): the Router sends that request to the service unpaid, reads the price it asks for, and returns an opaque quoteId, its short expiresAt, the rail (protocol), the network and merchant amount (settlement) and the fee-inclusive total (fee.capChargedCents, whole cents rounded up; fee.capChargedMicros exact, in 1/10,000 of a cent). Unlike the quote on a get_service endpoint (the last merchant price the catalog observed, routing fee excluded), this is priced live for your exact request and includes the fee. Because the request really reaches the service, a service that does not charge for it performs it, so take care quoting a method with side effects; and a quote spends the same per-service rate limit as a payment, so quote once per decision rather than polling. It prices the delegation pay_service would charge (optionSet: "delegation", naming its delegationId), or, with no delegation set up, what a personal crypto delegation would select (optionSet: "deployment"); in that case nextTool is setup_delegation: set one up and quote again before paying, since the delegation you create can select a different rail and price. It checks neither your remaining budget nor your wallet balance (see get_budget and wallet_balance). Next step (nextTool: "pay_service"): if fee.capChargedCents fits what you planned to spend, call pay_service before expiry with the same arguments, the quoted delegationId, quoteId, and maxTotalCents set to that figure as a number. The quote id fixes the exact challenge and fee-inclusive total while maxTotalCents remains an independent ceiling. paymentRequired: false means the service did not ask for payment for this request; upstreamStatus is its answer, and a non-2xx usually means the path, method or body is wrong. The service response itself is never returned. Outcomes, all charging nothing: {"payable":false}, service_not_found, catalog_unavailable and delegation_lookup_failed as in pay_service; quote_unavailable (no quote can be made here and retrying will not change that, so bound the price with pay_service maxTotalCents instead); quote_failed (the Router refused to price the call, or did not answer; see code, message and retryable); credential_refused (re-authorize). FUNDING (funding): chosen as pay_service would choose it. When you hold Nevermined credits that can pay it (a Nevermined Subscription allowance, welcome or top-up credits) and the endpoint accepts credits the answer is {"funding":"subscription","credits":…,"paymentRequired":…,"upstreamStatus":…}: the exact credits this request costs (the service is sent it unpaid; there is no quoteId or cent total). Credits follow each service’s live price, with a 1-credit minimum, so pass everything pay_service will send. Then call pay_service with the same arguments and the maxCredits this answer gives: a call that has become dearer is refused and charges nothing. paymentRequired: false means the service named no price for this request, and credits is then 0. The credits left of a subscriber in good standing are checked only when pay_service makes the call, so this answer does not promise the call will be paid with credits. Pass funding: "delegation" to price the delegation instead. Subscription refusals are named as in pay_service. When settlement.scheme is session, the merchant is paid out of a deposit in a payment channel, and sessionDeposit says what this call would do to it: action is open (the first call locks a deposit), top_up (it locks more), none (no new money leaves the wallet), closing (the call would be refused, nothing moves; quote again once it has closed) or null (what the call would do could not be stated, and pay_service may refuse it); approxCents is how much would move into the deposit, in cents, the network fee not included, and basis says whether that is sized for this budget and wallet or an upper_bound. That money can far exceed the price. It is locked, not spent, it is not charged to the budget, and what the merchant does not take comes back when the channel closes, idleCloseSeconds after its last use. Tell the human before paying. Requires your Nevermined API key on the Authorization header.

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": {
      "slug": "<slug>"
    },
    "name": "quote_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoThe request payload you would send; some services price by it.
pathNoThe same `path` you would pass to pay_service: read `get_service`'s `requestShape.endpoints[].payServiceArgs.path` and replace every `pathParams` placeholder. Put query parameters in `search`.
slugYesThe service slug to quote.
methodNoHTTP method. Omit to use the method the catalog records for the endpoint matching `path` (POST when it records none), exactly as pay_service does.
searchNoQuery string without ?, for a slug-routed GET (e.g. flight_iata=AA217).
fundingNoWhat to price: `subscription` (your Nevermined credits) or `delegation` (the fee-inclusive money total). Omit it to price the funding pay_service would use.
headersNoThe extra headers you would send to the vendor.
delegationIdNoThe delegation you would pay with, when you authenticate with an API key; defaults to the one pay_service would use. A card or organization-wallet delegation can select a different rail, and so a different price. An OAuth-connected caller is always quoted for the grant it approved, so a value here does not choose the delegation; the result names the one priced.
requireProtocolNoPrice (and pin the returned quote to) one payment rail. Pass the same value you will pass to pay_service: the quote prices that rail, and the quoteId it returns is only payable on it. If the service does not offer the pinned rail the quote is refused (`quote_failed` with code BCK.ROUTER.0045, nothing charged) rather than priced on the other one. Omit to let the Router auto-select (it prefers mpp).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / requireProtocol / description
      Previous value: -"Price (and pin the returned quote to) one payment rail. Pass the same value you will pass to pay_service: the quote prices that rail, and the quoteId it returns is only payable on it. If the service does not offer the pinned rail the quote is refused (`quote_failed` with code BCK.ROUTER.0045, nothing charged) rather than priced on the other one. Omit to let the Router auto-select (it prefers mpp). A subscription-credit quote (`funding: \"subscription\"`) is rail-agnostic — it prices the published credit tariff, so the pin does not change it and is not applied here; the subsequent paid call still enforces the pin and can be refused if the service does not offer it."New value: +"Price (and pin the returned quote to) one payment rail. Pass the same value you will pass to pay_service: the quote prices that rail, and the quoteId it returns is only payable on it. If the service does not offer the pinned rail the quote is refused (`quote_failed` with code BCK.ROUTER.0045, nothing charged) rather than priced on the other one. Omit to let the Router auto-select (it prefers mpp)."
  2. Changed1 schema field changed
    • addedInput schema / properties / requireProtocol
      Added value: +{
      +  "description": "Price (and pin the returned quote to) one payment rail. Pass the same value you will pass to pay_service: the quote prices that rail, and the quoteId it returns is only payable on it. If the service does not offer the pinned rail the quote is refused (`quote_failed` with code BCK.ROUTER.0045, nothing charged) rather than priced on the other one. Omit to let the Router auto-select (it prefers mpp). A subscription-credit quote (`funding: \"subscription\"`) is rail-agnostic — it prices the published credit tariff, so the pin does not change it and is not applied here; the subsequent paid call still enforces the pin and can be refused if the service does not offer it.",
      +  "enum": [
      +    "x402",
      +    "mpp"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / funding / description
      Previous value: -"What to price: `subscription` (credits from your Nevermined Subscription) or `delegation` (the fee-inclusive money total). Omit it to price the funding pay_service would use."New value: +"What to price: `subscription` (your Nevermined credits) or `delegation` (the fee-inclusive money total). Omit it to price the funding pay_service would use."
  4. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / headers / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / funding
      Added value: +{
      +  "description": "What to price: `subscription` (credits from your Nevermined Subscription) or `delegation` (the fee-inclusive money total). Omit it to price the funding pay_service would use.",
      +  "enum": [
      +    "subscription",
      +    "delegation"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond `readOnlyHint: true`, the description discloses that the tool charges nothing, signs nothing, reserves no budget, forwards the real request to the service, can trigger side effects, shares the payment rate limit, requires an API key, and does not check budget or wallet balance. It also explains funding modes, session deposit effects, failure outcomes, and what is never returned.

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?

The definition is front-loaded with purpose and key behavior, but it is a very long, dense block that repeats framing such as 'all charging nothing' and 'as in pay_service.' The content is largely justified by tool complexity, but it is not concise and would benefit from headings or bullets.

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?

With no output schema, the description carries the full burden and does so thoroughly: it describes return fields, pricing semantics, funding variants, session-deposit behavior, failure outcomes, prerequisites, and next steps. Nothing an agent needs in order to call or interpret this tool correctly appears to be 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?

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning: it says to pass the same arguments as `pay_service`, explains the `funding` choice, clarifies `delegationId` behavior for OAuth versus API-key callers, and describes how `quoteId` and `maxTotalCents` interact. It does not explicitly discuss `requireProtocol` beyond the schema, keeping it from a 5.

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 opens with a precise verb and resource: 'Price ONE call to a catalog service WITHOUT paying it.' It explicitly distinguishes this from `pay_service` and from the `quote` on a `get_service` endpoint, so an agent can select it without inspecting sibling schemas.

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 states exactly when to use this tool (to price before paying), when not to (it is not a payment), and names alternatives such as `pay_service`, `get_service`, `setup_delegation`, `get_budget`, and `wallet_balance`. It also gives the next step and cautions against polling the shared rate limit.

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.

Resources