Skip to main content
Glama

Last Price

Server Details

Compute and verify prices from an agent, metered per call. Works keyless on a demo tenant.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 10 tools

Disambiguation4/5

Each tool has a mostly distinct role: compute_price produces a price, verify_price judges one, report_outcome closes the loop, and the auth/meta tools (register_agent, use_api_key, search_tools, call_tool) are separable. The only soft overlaps are search_tools vs call_tool (find vs execute) and pricing_conversation vs compute_price (prepare vs compute), both clarified by descriptions.

Naming Consistency4/5

Nine of ten tools follow a clear snake_case verb_noun pattern (compute_price, get_receipt, list_functions, register_agent, report_outcome, use_api_key, verify_price, search_tools, call_tool). The single noun-only outlier, pricing_conversation, breaks the pattern but is still readable and unambiguous.

Tool Count4/5

Ten exposed tools is a well-scoped surface for the core pricing workflow. The set is partly a gateway (search_tools/call_tool front 300+ hidden tools), which keeps the visible count lean but means two of the ten are dispatchers rather than domain operations.

Completeness4/5

The lifecycle is largely covered: onboarding (register_agent/use_api_key), discovery (list_functions), pricing (compute_price), adjudication (verify_price), clarification (pricing_conversation), and post-sale (get_receipt/report_outcome). The notable gap is that get_receipt and report_outcome depend on a usage event id from list_usage_events, which is not exposed directly and must be reached via search_tools/call_tool.

Available Tools

10 tools
call_toolA
Destructive
Inspect

Run any Last Price tool by name, including one this connection does not list. Find the name and its arguments with search_tools first. What it does, and whether it changes anything, is what that tool says.

Inputs: name (required), arguments. Returns: message

compute_priceAInspect

Compute a price. Returns the price, the function that produced it, the metered cost and a trace of each stage. Send currency plus unit_cost (what the work costs you) or current_price. Missing inputs return an error naming them. For a competitor offer, put competitor_price, competitor_currency and competitive_action in metadata. To pay for this one call with x402, pass payment (call without it to read the price). A result with valid_until (RFC 3339) holds only until then. confidence is the function's own 0 to 1 score for its price, not a probability that a buyer accepts. price_statement says what the answer is: a third party's estimate for you, or the workspace's commitment when a signed quote is attached.

Inputs: currency (required), geo, payer, intent, +23 more. Returns: kind, message, receipt, currency, +10 more

get_receiptA
Read-onlyIdempotent
Inspect

Get the receipt for one of your workspace's priced calls, by its usage event id (the id list_usage_events returns and report_outcome takes): what was priced, by which function and agent, when, the amount, how it was paid, and the outcome if one was reported. Receipts are made only when you ask, never sent for every call. For CSV or a printable page, call GET /api/receipts/{id} with format=csv or format=html. Needs a Last Price credential with price compute or billing read scope. Needs a claimed workspace: a sandbox key from self-registration is refused (403) until a person claims the workspace.

Inputs: usage_event_id (required). Returns: issuer, object, message, receipt, +1 more

list_functionsB
Read-onlyIdempotent
Inspect

List the pricing functions registered for the authenticated tenant.

Inputs: limit, offset, status, is_builtin, +1 more. Returns: items, message, functions

pricing_conversationAInspect

Ask Last Price what pricing inputs are missing. Start with request: {}, return its questions to the caller, then send continuation.request and answers. Prepare is free and does not compute. When ready, action compute uses the existing authenticated pricing API; configure a credential first. Never invent answers or treat a continuation as authorization.

Inputs: action, answers, request. Returns: result, status, message, questions, +3 more

register_agentAInspect

Sign up with no key and no human: creates a sandbox workspace of your own and returns its API key (shown once), its daily limits and a claim link a person can open to take the workspace into their account. Pass name (2 to 64 characters, such as your-system/role-name), and optionally contact_email and intended_use. On the hosted MCP server this session goes on using the new key, so the tools that need a credential work at once with no header to add; elsewhere send the returned key as the x-api-key header. Public: needs no credential.

Inputs: name (required), intended_use, contact_email.

report_outcomeAInspect

Report whether a price from compute_price was used: once the buyer has accepted or turned down a price, report it. Pass receipt.id from that result as usage_event_id, or omit it to report the last price compute_price returned on this connection or tools instance, once (the hosted MCP endpoint remembers nothing, so pass it there). Outcomes are what later routing and confidence learn from. With outcome pricing on, a rejection within the call's outcome window gives back part of what it cost; the result says what was refunded. Needs a Last Price credential. Report only what actually happened. Needs a claimed workspace: a sandbox key from self-registration is refused (403) until a person claims the workspace.

Inputs: outcome (required), evidence_url, evidence_note, quality_score, +2 more. Returns: event, message, quote_expired, outcome_window, +1 more

search_toolsA
Read-onlyIdempotent
Inspect

Find the Last Price tool for a task. This connection lists only the tools that reach a price; the server has over 300 more (pricing functions, routing, experiments, webhooks, billing, orders, the marketplace and more). Pass query, a few words for the job, and get back the best matching tools with their full input schemas. Then call one with call_tool, or by its name. With no query it lists every tool name.

Inputs: limit, query. Returns: hint, query, tools, message

use_api_keyA
Idempotent
Inspect

Use a Last Price API key you already hold (a saved file, LASTPRICE_API_KEY) in this MCP connection, when it was opened without one: pass api_key. On the hosted MCP server this session then runs as that key's agent, so the tools that need a credential work at once with no header to add; it lasts until the session ends or the key is revoked or rotated. The key is checked, never echoed back. A connection that already has a credential keeps it. Public: needs no other credential.

Inputs: api_key (required).

verify_priceAInspect

Ask whether a price makes sense for its context, rather than what the price should be. Returns a verdict (within_band, too_high, too_low, or unknown), the band it was judged against, a signed deviation from the reference, a confidence, and the evidence behind it. A verdict of "unknown" means the price could not be judged, which is not the same as within_band. Act on next_step: buy (within band on confident, independent evidence), negotiate (too high), walk_away (far too high, confidently) or check_more (unknown, too low, or weak evidence); next_step_reason says why. Pass quote_valid_until from the compute_price result the price came from, and where quote expiry is switched on the answer says quote_expired when that quote is stale. Where paid verdicts are switched on, a caller with no key can pay for one verdict with x402: pass payment, a signed payment for the price and terms listed under payments.x402.verify_price in /.well-known/agents.json; a verdict of unknown is not charged. Where buyers' spend limits are switched on and metadata.category names a category, the evidence includes buyer_budget: what buyers' own spend checks allowed for it (buyer_envelope), reported and never counted in the verdict. price_statement says what the answer is: a third party's estimate whose band is an acceptance range around the reference, not an interval of value.

Inputs: proposed_price (required), geo, channel, payment, +12 more. Returns: band, message, verdict, currency, +10 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources