Skip to main content
Glama

Send quote

o2c_send_quote
Destructive

Mark a quote as sent to the customer. This records that it went out. It does not send anything — this system has no outbound channel, by design. Effects: quote.status -> sent.

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

Input Schema

NameRequiredDescriptionDefault
quote_idYesThe quote. An existing quote id.

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=false, destructiveHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond that: the exact state transition ('quote.status -> sent') and the crucial caveat that no outbound channel exists, which prevents the agent from believing an email is dispatched. It does not address what happens on a repeat call, which matters given idempotentHint=false.

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 lines, front-loaded with the action, followed by the caveat and the effect. Every sentence earns its place and nothing is redundant.

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 one-parameter state-mutation tool with no output schema, the description covers purpose, the key misconception, and the resulting state. The remaining gap is the non-idempotent behavior — whether a second call on an already-sent quote errors — which an agent would want to know before retrying.

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 100% and the single parameter's meaning ('An existing quote id') is fully documented in the schema. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 ('Mark a quote as sent') and immediately disambiguates it from what the name implies by clarifying it does not actually transmit anything. An agent can tell exactly what this tool does 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?

The description gives clear context for when to call it (recording that a quote went out) and explicitly rules out the outbound-delivery use case that the name 'send' would otherwise suggest. It does not name any sibling alternative or state preconditions such as the quote's required prior status.

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.