Skip to main content
Glama

Get quote checklist

get_quote_checklist
Read-onlyIdempotent

Use when someone wants quotes for building, repair or renovation work, or for property services such as land surveys and appraisals, in the United States. Returns the details contractors need so you can ask the person for them.

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": {
      "job": "<job>"
    },
    "name": "get_quote_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesShort description of the work, such as 'replace a roof'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: it is US-scoped and returns contractor-needed details so the agent can ask the person for them, implying it does not create or submit a quote. It does not describe exact return fields.

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, front-loaded with the usage condition and followed by the return purpose. There is no repetition or wasted text.

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 simple read-only, one-parameter helper with rich annotations, the description covers when to use it and what it provides. Minor gaps remain around how it relates to create_quote_request and the exact shape of the returned checklist.

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 'job' parameter already has a clear description and example ('replace a roof'). The tool description adds no additional meaning about the parameter, so the baseline of 3 is appropriate.

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 the tool returns the details/checklist contractors need in order to provide a quote for building, repair, renovation, or property services. It is more specific than the name alone, but it does not explicitly distinguish this read-only checklist from the sibling create_quote_request tool.

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 a clear trigger: 'Use when someone wants quotes' for the listed work types in the United States. It does not explicitly state when not to use it or name create_quote_request as the alternative for submitting a request.

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