Skip to main content
Glama

Quote options for a job or symptom

quote_order
Read-only

USE THIS when the human describes a job or a symptom rather than a product ("my router bits are burning the wood", "I keep snapping 3mm drills") and gives a budget. Turns that into 2-4 priced options with a one-line reason for each.

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": {
      "need": "<need>"
    },
    "name": "quote_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
needYesthe job or symptom in plain words
ships_toNoUS
budget_maxNo
product_idNooptional: quote one exact SKU instead of a need

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description then adds genuinely new behavior: the result is 2-4 options, each with a one-line reason, derived from a stated budget. It omits what happens when no budget is supplied and whether pricing includes shipping/tax, which matters for a read-only quoting tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the trigger condition is front-loaded before the outcome description. Both example phrases add disambiguation value rather than padding.

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 five-parameter, no-output-schema tool, the description covers when to call it, what inputs matter, and what comes back (2-4 reasoned options). The gaps are the undocumented qty/ships_to semantics and the absence of any note about missing-budget behavior.

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 coverage is only 40%, so the description must compensate; it does clarify the 'need' field (job/symptom in plain words), the role of budget, and that product_id is a mutually exclusive alternative to need. It says nothing about qty or ships_to, leaving two of five parameters to bare schema defaults with only 40% coverage overall.

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?

States a specific transformation: takes a plain-language job or symptom plus a budget and returns 2-4 priced options with a one-line rationale for each. This is a clear verb+resource+output shape that an agent can distinguish from product-oriented siblings like search_products or get_product without opening the schema.

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?

Gives an explicit trigger condition ('USE THIS when the human describes a job or a symptom rather than a product') with concrete example utterances and the budget prerequisite. It does not name a concrete alternative tool for the product-lookup case, leaving the agent to infer that search_products/get_product are the fallback, so it falls short of the full 5.

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