Skip to main content
Glama

accept_quote

Accept a quote. IMPORTANT: this does not confirm execution. The request enters pending_review; a human operator confirms or declines each request individually during the launch phase. No timeline is promised. Poll get_task_status for the outcome.

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>",
      "access_token": "<access_token>"
    },
    "name": "accept_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYes
access_tokenYesThe access_token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses that acceptance is not execution, that requests enter pending_review with human confirmation or decline during launch, that no timeline is promised, and that get_task_status is the polling mechanism.

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?

Four short sentences, front-loaded with the action and then the critical caveat. Every sentence contributes: caveat, review process, timeline, and next step.

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 quote-acceptance tool with no annotations or output schema, the description supplies the critical async/human-review behavior and the polling path. It is only incomplete on parameter sourcing, notably quote_id, which is partly covered by the access_token schema description.

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

Parameters2/5

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

Schema coverage is 50%: access_token is described in the schema, while quote_id is not. The description adds no parameter-specific meaning—no format, source, or constraints for quote_id—so it does not compensate for the coverage gap.

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?

The description opens with a specific verb and resource ('Accept a quote'), and the accept/decline/request distinction is clear from the sibling names. An agent can tell this is the affirmative quote action 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?

It gives important post-call context (enters pending_review; poll get_task_status for the outcome) but does not explicitly say when to prefer this over decline_quote or request_quote. The implied usage is clear, but alternatives are not named.

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