Skip to main content
Glama

Start a quote request

start_quote
Read-only

Make a link that opens the Flathead Trades quote form already filled with the work, the town and the description. The person finishes it and agrees to be contacted themselves; the request is then offered live to one local pro at a time who is on right now, the first to take it calls them, and they follow it on a private request page. Free for homeowners.

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": {
      "trade": "<trade>"
    },
    "name": "start_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoThe town in the Flathead Valley.
tradeYesThe kind of work.
descriptionNoWhat needs doing, in the person’s words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds substantial behavioral context beyond that: the link opens a pre-filled form, the person completes and consents to contact, the request is offered live to one local pro at a time, and follow-up happens on a private request page. This clarifies the full lifecycle without contradicting the read-only annotation.

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 the core action and avoids boilerplate. The second sentence carries useful workflow context, though it is fairly long and could be tightened without losing much.

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?

For a simple, read-only link generator with three fully documented parameters and no output schema, the description is complete. It explains what the tool does, what gets pre-filled, and what happens after the link is used, leaving no critical gap for an agent.

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%, so all three parameters are already documented. The description maps the fields conceptually ('work, the town and the description'), but adds no format or constraint details beyond what the schema already provides. Baseline 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 states a specific action and resource: it makes a link that opens a pre-filled quote form for Flathead Trades. The downstream workflow is explained, but it does not explicitly distinguish this tool from siblings like find_pros or list_trades_and_towns.

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

Usage Guidelines3/5

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

The description implies this is for homeowners initiating a quote request and notes it is free for homeowners, but it gives no explicit when-to-use guidance or comparison against find_pros / list_trades_and_towns. The usage context is inferable, not stated.

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