compu-ai-mcp

create_quote

Generate a formal quote for a customer with an optional instalment plan, returning a quote code for presentation.

Instructions

Create a formal quote for a customer, optionally under an instalment plan. Returns a quote code that can be given to the customer. This writes to the database.

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": {
      "customer": "<customer>",
      "sku": "<sku>"
    },
    "name": "create_quote"
  }
}

Input Schema

Name	Required	Description
`sku`	Yes
`plan_id`	No	Optional instalment plan.
`customer`	Yes	Customer name.
`quantity`	No	Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description explicitly notes 'This writes to the database', which is important because readOnlyHint is false. It also discloses the return value (quote code). It does not describe idempotency, but the annotations already indicate idempotentHint is false.

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 concise and well-structured, covering the action, optional parameter, return value, and side effect in three short sentences with no unnecessary detail.

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?

Even without an output schema, the description mentions the returned quote code and states the database write. It is sufficient for basic invocation, though it does not cover prerequisites, error behavior, or when a quote should be created instead of an order.

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?

The schema already describes customer, plan_id, and quantity. The description adds little beyond 'optionally under an instalment plan', which mirrors the schema. The sku parameter has no description, though its name is self-explanatory.

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?

Clearly states the action ('Create a formal quote'), the target (customer/plan), and the return value (quote code). It also explicitly says it writes to the database, making the tool's purpose unambiguous and distinct from order creation.

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

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool versus alternatives like create_order, or when to first consult list_installment_plans. The description relies on the tool name and sibling context rather than stating usage conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server