Skip to main content
Glama

Request a quote

request_quote

Ask an entry for a quote for the user: a price for a job they describe. Only for entries whose actions (get_entry_sections) list request_quote. Ask the user for their name and email address, and add a budget only if they give one. Nothing is sent by this call: the user sends it on Daawid's page, with a code Daawid emails them. Give the user the link from the answer.

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": {
      "entry": "<entry>",
      "requester": "<requester>",
      "description": "<description>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich entry: its ID or slug, from search or get_entry.
budgetNoThe most they want to spend, if they say. Ask for the currency; don't assume one.
answersNoAnswers to the action's own questions (get_entry_sections), by their keys.
actionIdNoWhich of its actions of this kind (get_entry_sections), when it has several.
requesterYes
offeringIdNoWhich of the entry's offerings (get_entry_sections) it is about, if one.
postalCodeNoThe postal code where the work is, when the user gives it or the action asks for one.
descriptionYesThe job, in the user's words and language: what it is, how big, what else changes the price. Show it to them; don't add what they didn't say.
desiredTimingNoWhen they would like it done, in their words: "February or March".
idempotencyKeyNoYour own key for this request: the same key and details within 24 hours give the same request.

Output Schema

NameRequiredDescriptionDefault
urlNo
kindYes
entryYes
runIdNo
statusYes
summaryYes
expiresAtNo
confirmUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare a non-read-only, open-world, non-idempotent call, and the description adds the crucial fact that 'Nothing is sent by this call' — the user completes submission on Daawid's page with an emailed code. That is exactly the kind of consequence an agent could not infer from the hints, and it also tells the agent to surface the returned link.

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?

Front-loaded with the purpose, then the gating condition, then the behavioral caveat and the follow-up instruction. Dense and mostly waste-free, though the middle sentences pack several instructions together and read as a run-on.

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 10-parameter, nested-object, open-world mutation with an output schema, the description covers the gating check, the user-interaction protocol, the non-submission semantics, and what to do with the response. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 90%, so the baseline is 3; the description still adds meaning by telling the agent to solicit requester name/email and to include budget only when volunteered. It does not explain answers, actionId, or offeringId beyond the schema, so it stops short of a 5.

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 verb and resource ('Ask an entry for a quote... a price for a job they describe') and implicitly separates itself from request_appointment/request_callback by naming the quote action. An agent can identify the operation 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 Guidelines5/5

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

Gives an explicit precondition: 'Only for entries whose actions (get_entry_sections) list request_quote', naming the sibling that gates it. It also states the interaction rules (ask for name and email, add a budget only if given), so the when and how are both covered.

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