Skip to main content
Glama

Last Price

verify_price

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.

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": {
      "proposed_price": "<proposed_price>"
    },
    "name": "verify_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoOptional geography hint, e.g. US.
channelNoOptional. The sales channel, e.g. an agent marketplace. With a rate saved by set_channel_rates, the price covers the channel's cut.
paymentNoOptional. The signed x402 payment, base64, as sent in an X-PAYMENT or PAYMENT-SIGNATURE header; or, where the answer offers MPP tempo, the whole Payment-Authorization value ("Payment " and the credential). Omit it to read what the call costs and how to pay; nothing is charged until you send it.
currencyNoThree-letter ISO currency code, e.g. USD. Defaults to USD.
metadataNoOptional free-form context.
max_priceNoOptional hard ceiling. Binding: a verdict will never relax it.
min_priceNoOptional hard floor. Binding: a verdict will never relax it.
buyer_typeNoOptional. Who the price is for: an AI agent or a person. Recorded with the quote only.
product_idNoOptional identifier of what is being priced.
buyer_agentNoOptional. The buying agent, e.g. chatgpt. A label recorded with the quote only.
product_typeNoOptional category of what is being priced.
current_priceNoOptional incumbent price. Not required: asking whether a price is sensible does not presuppose an existing one.
outcome_termsNoOptional, for a price charged per outcome: when the outcome counts as failed and what is owed then. The result echoes the terms normalised, with complete false until success_definition, resolve_by and on_timeout are all set.
proposed_priceYesThe price to judge. This is the subject of the call.
customer_segmentNoOptional segment, e.g. enterprise.
quote_valid_untilNoOptional. The valid_until of the compute_price result this price came from (RFC 3339). Where quote expiry is switched on, a time already past is answered with quote_expired: true.

Output Schema

NameRequiredDescriptionDefault
bandNoThe range the price was judged against; a null bound is open on that side. Term: lp:band.verification.
messageNoA short sentence about the result that an agent can show its person.
verdictNounknown means nothing could judge the price, which is not within_band. Term: lp:verdict.
currencyNoISO 4217 code of proposed_price and the band.
evidenceNoEach source's reference, band and weight. Term: lp:evidence.
next_stepNoWhat a buyer should do with this price. Term: lp:next-step.
confidenceNoThe lowest evidence weight, halved when sources disagree. Term: lp:confidence.verdict.
valid_untilNoRFC 3339; the verdict holds only until then.
deviation_pctNoPercent from the reference price; positive is above it. Term: lp:deviation.
proposed_priceNoThe price that was judged. Term: lp:proposed-price.
price_statementNoWhat this answer is: a third party's estimate whose band is an acceptance range around the reference (interval_meaning acceptance_range), not an interval of value. Term: lp:price-statement.
reference_priceNoThe price the evidence points at. Term: lp:reference-price.
next_step_reasonNoWhy next_step was chosen, in one sentence.
independent_evidenceNoFalse means the verdict partly reasoned from the price itself. Term: lp:independent-evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / currency / description
      Added value: +"ISO 4217 code of proposed_price and the band."
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
    • addedOutput schema / properties / next_step_reason / description
      Added value: +"Why next_step was chosen, in one sentence."
    • addedOutput schema / properties / price_statement
      Added value: +{
      +  "description": "What this answer is: a third party's estimate whose band is an acceptance range around the reference (interval_meaning acceptance_range), not an interval of value. Term: lp:price-statement.",
      +  "properties": {
      +    "audience": {
      +      "enum": [
      +        "public",
      +        "one_counterparty",
      +        "private"
      +      ],
      +      "type": "string"
      +    },
      +    "interval_meaning": {
      +      "enum": [
      +        "credible_interval",
      +        "evidence_spread",
      +        "acceptance_range",
      +        "negotiation_room"
      +      ],
      +      "type": "string"
      +    },
      +    "speaker": {
      +      "enum": [
      +        "seller",
      +        "buyer",
      +        "both",
      +        "third_party",
      +        "market"
      +      ],
      +      "type": "string"
      +    },
      +    "standing": {
      +      "enum": [
      +        "proposal",
      +        "commitment",
      +        "executed",
      +        "estimate",
      +        "constraint"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "speaker",
      +    "standing",
      +    "audience"
      +  ],
      +  "type": "object"
      +}
  2. Changed14 schema fields changed
    • addedOutput schema / properties / band
      Added value: +{
      +  "description": "The range the price was judged against; a null bound is open on that side. Term: lp:band.verification.",
      +  "properties": {
      +    "lower": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "upper": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / confidence / description
      Added value: +"The lowest evidence weight, halved when sources disagree. Term: lp:confidence.verdict."
    • addedOutput schema / properties / confidence / maximum
      Added value: +1
    • addedOutput schema / properties / confidence / minimum
      Added value: +0
    • addedOutput schema / properties / deviation_pct
      Added value: +{
      +  "description": "Percent from the reference price; positive is above it. Term: lp:deviation.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / evidence
      Added value: +{
      +  "description": "Each source's reference, band and weight. Term: lp:evidence.",
      +  "type": "array"
      +}
    • addedOutput schema / properties / independent_evidence
      Added value: +{
      +  "description": "False means the verdict partly reasoned from the price itself. Term: lp:independent-evidence.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / next_step
      Added value: +{
      +  "description": "What a buyer should do with this price. Term: lp:next-step.",
      +  "enum": [
      +    "buy",
      +    "negotiate",
      +    "walk_away",
      +    "check_more"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / next_step_reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / proposed_price / description
      Added value: +"The price that was judged. Term: lp:proposed-price."
    • addedOutput schema / properties / reference_price / description
      Added value: +"The price the evidence points at. Term: lp:reference-price."
    • addedOutput schema / properties / valid_until
      Added value: +{
      +  "description": "RFC 3339; the verdict holds only until then.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdict / description
      Added value: +"unknown means nothing could judge the price, which is not within_band. Term: lp:verdict."
    • addedOutput schema / properties / verdict / enum
      Added value: +[
      +  "within_band",
      +  "too_high",
      +  "too_low",
      +  "unknown"
      +]
  3. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / buyer_agent / description
      Previous value: -"Optional. The buying agent, e.g. chatgpt or agent.example.com. A label recorded with the quote only (while its release flag is on); never sent to the pricing function."New value: +"Optional. The buying agent, e.g. chatgpt. A label recorded with the quote only."
    • changedInput schema / properties / channel / description
      Previous value: -"Optional. The sales channel the price is for, such as a shopping agent or an agent marketplace. When your workspace saved a rate for it with set_channel_rates and channel pricing is on, the price is raised so you keep the same amount after the channel's cut."New value: +"Optional. The sales channel, e.g. an agent marketplace. With a rate saved by set_channel_rates, the price covers the channel's cut."
    • changedInput schema / properties / outcome_terms / description
      Previous value: -"Optional, for a price charged per outcome. When the outcome counts as failed and what is owed then. Where outcome terms are switched on for the workspace, the result carries outcome_terms: these terms normalised, the deadline as a time, the amount owed on timeout, and which terms are missing (complete is false without success_definition, resolve_by and on_timeout). Sending it marks the price as an outcome price; so does metadata.unit \"outcome\"."New value: +"Optional, for a price charged per outcome: when the outcome counts as failed and what is owed then. The result echoes the terms normalised, with complete false until success_definition, resolve_by and on_timeout are all set."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "confidence": {
      +      "type": "number"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "proposed_price": {
      +      "type": "number"
      +    },
      +    "reference_price": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "verdict": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / payment
      Added value: +{
      +  "description": "Optional. The signed x402 payment, base64, as sent in an X-PAYMENT or PAYMENT-SIGNATURE header; or, where the answer offers MPP tempo, the whole Payment-Authorization value (\"Payment \" and the credential). Omit it to read what the call costs and how to pay; nothing is charged until you send it.",
      +  "maxLength": 8192,
      +  "minLength": 20,
      +  "type": "string"
      +}
  5. Changed5 schema fields changed
    • addedInput schema / properties / buyer_agent
      Added value: +{
      +  "description": "Optional. The buying agent, e.g. chatgpt or agent.example.com. A label recorded with the quote only (while its release flag is on); never sent to the pricing function.",
      +  "maxLength": 100,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / buyer_type
      Added value: +{
      +  "description": "Optional. Who the price is for: an AI agent or a person. Recorded with the quote only.",
      +  "enum": [
      +    "agent",
      +    "person",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / channel
      Added value: +{
      +  "description": "Optional. The sales channel the price is for, such as a shopping agent or an agent marketplace. When your workspace saved a rate for it with set_channel_rates and channel pricing is on, the price is raised so you keep the same amount after the channel's cut.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / outcome_terms
      Added value: +{
      +  "description": "Optional, for a price charged per outcome. When the outcome counts as failed and what is owed then. Where outcome terms are switched on for the workspace, the result carries outcome_terms: these terms normalised, the deadline as a time, the amount owed on timeout, and which terms are missing (complete is false without success_definition, resolve_by and on_timeout). Sending it marks the price as an outcome price; so does metadata.unit \"outcome\".",
      +  "properties": {
      +    "evidence": {
      +      "description": "What proves the outcome, e.g. [\"delivery_receipt\"].",
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 10,
      +      "type": "array"
      +    },
      +    "on_timeout": {
      +      "description": "What is owed when the deadline passes without success.",
      +      "enum": [
      +        "no_charge",
      +        "partial",
      +        "full"
      +      ],
      +      "type": "string"
      +    },
      +    "resolve_by": {
      +      "description": "The deadline: an ISO 8601 duration from the quote (P30D, PT48H) or an RFC 3339 time. After it, with no success, the outcome has failed.",
      +      "type": "string"
      +    },
      +    "success_definition": {
      +      "description": "What the buyer must see for the outcome to count.",
      +      "maxLength": 500,
      +      "type": "string"
      +    },
      +    "timeout_share": {
      +      "description": "With on_timeout \"partial\": the fraction of the price owed, e.g. 0.3 for 30%.",
      +      "exclusiveMaximum": 1,
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / quote_valid_until
      Added value: +{
      +  "description": "Optional. The valid_until of the compute_price result this price came from (RFC 3339). Where quote expiry is switched on, a time already past is answered with quote_expired: true.",
      +  "format": "date-time",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the verdict values, what unknown means, how next_step should be interpreted, quote-expiry behavior, x402 payment behavior, and that unknown verdicts are not charged. These are meaningful behavioral details for a tool whose annotations mark it as non-read-only and open-world.

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?

The description is dense and front-loads the purpose, return values, and next-step guidance, and most sentences carry useful information. It is longer than typical because the tool has complex payment and verification modes, but the single-paragraph structure makes it somewhat harder to scan.

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?

Given the tool's complexity, 16 parameters, and rich output schema, the description covers the critical behavioral context: verdict semantics, next steps, quote expiry, payment, and buyer-budget evidence. It does not need to explain return values in full because an output schema exists.

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 for key parameters such as proposed_price being the subject, quote_valid_until coming from compute_price, payment using x402, and metadata.category triggering buyer_budget evidence. It does not need to restate every schema-described field.

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 verb and resource: verifying whether a price makes sense for its context. It explicitly contrasts this with computing what the price should be, which distinguishes it from the sibling compute_price tool.

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?

The opening sentence tells the caller when to use this tool versus compute_price, and later text explains the workflow by saying to pass quote_valid_until from the compute_price result. It also gives concrete guidance on acting on next_step values and when a paid verdict applies.

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