Skip to main content
Glama

Last Price

pricing_conversation

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.

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": "pricing_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoprepare (free) returns the questions still open; compute prices once nothing is missing.prepare
answersNoAnswers to the questions the last call asked, by field, e.g. {"currency":"USD","unit_cost":4}.
requestNoPartial REST PricingComputeRequest, including nested context, constraints, an explicit function selection and options. Reuse continuation.request on subsequent calls.

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
messageNoA short sentence about the result that an agent can show its person.
questionsNo
assumptionsNo
explanationNo
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
  2. Changed3 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"prepare (free) returns the questions still open; compute prices once nothing is missing."
    • addedInput schema / properties / answers / description
      Added value: +"Answers to the questions the last call asked, by field, e.g. {\"currency\":\"USD\",\"unit_cost\":4}."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "assumptions": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "continuation": {
      +      "properties": {
      +        "request": {
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "explanation": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "questions": {
      +      "items": {
      +        "properties": {
      +          "field": {
      +            "type": "string"
      +          },
      +          "question": {
      +            "type": "string"
      +          },
      +          "reason": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "result": {
      +      "properties": {
      +        "computed_price": {
      +          "type": "number"
      +        },
      +        "confidence": {
      +          "type": "number"
      +        },
      +        "currency": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "enum": [
      +        "needs_input",
      +        "ready",
      +        "completed",
      +        "unable_to_assess"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: prepare is free and does not compute, compute uses the authenticated pricing API, credentials must be configured, and continuation must not be treated as authorization. It also explicitly forbids inventing answers.

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 front-loaded with purpose and then explains the prepare/compute flow, credential prerequisite, and safety rule. It is dense but mostly efficient, with minor awkwardness from phrases such as 'return its questions to the caller.'

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?

For a complex tool with nested request objects, an output schema, and workflow actions, the description covers the essential preparation, computation, authentication, and safety behavior. It could be stronger by explicitly relating this tool to sibling pricing tools.

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 100% schema description coverage, the schema already documents the parameters well. The description still adds useful workflow meaning for action, request reuse via continuation.request, and answers to the questions asked by the previous call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool asks Last Price which pricing inputs are missing and supports prepare versus compute actions. It does not explicitly distinguish the tool from sibling tools such as compute_price or verify_price, so it is clear but lacks sibling differentiation.

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?

It gives concrete usage steps: start with request {}, return questions, then send continuation.request and answers, and only use compute when ready. It also states that prepare is free and that a credential must be configured first, though it does not name sibling alternatives.

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