Skip to main content
Glama

Get Quote Tool

get-quote
Read-only

Returns one authorized estimate with bounded customer, status, pricing, revision, and line-item fields; addresses, notes, and terms are excluded. Use to get quote in the connected business. Returns quote, scope.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "get-quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesEstimate ID returned by search-quotes.

Output Schema

NameRequiredDescriptionDefault
quoteYesQuote data returned by the authorized safe projection.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "quote_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "quote": {
      +      "description": "Quote data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "quote",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: it discloses the scope of returned data ('bounded ... fields') and explicitly names excluded data (addresses, notes, terms), which tells the agent what it will not get back and therefore when it needs another tool.

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 first sentence is front-loaded and dense with useful detail. The second sentence is redundant filler that repeats the name, and the trailing 'Returns quote, scope.' is cryptic shorthand that adds little. Roughly half the text earns its place.

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?

This is a simple single-parameter read tool with an output schema, so return-value documentation is not the description's burden, and it still helpfully signals which fields are included. Annotations cover the safety profile and the parameter is fully documented in schema. The only real gap is the absence of routing guidance versus preview-quote.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is documented in the schema itself, including its provenance ('Estimate ID returned by search-quotes'). The description adds no format, range, or sourcing detail beyond that, so the baseline 3 applies.

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 first sentence gives a specific verb and resource ('Returns one authorized estimate') and enumerates the field groups included (customer, status, pricing, revision, line items) as well as what is excluded (addresses, notes, terms). That is far more than a restatement of the name. It stops short of naming a sibling to distinguish itself from, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage statement is 'Use to get quote in the connected business,' which is a restatement of the tool name rather than guidance. Nothing tells the agent when to pick this over preview-quote, nor what the precondition is (a valid quote_id from search-quotes appears only in the schema, not the description).

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