Skip to main content
Glama
Sign In
dVersum MCP Server

dVersum MCP Server

Official
by dversum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_quote_line_item

Add a line item to an existing quote by specifying description, quantity, unit price, and optional tax rate.

Instructions

Add a line item to a quote.

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>",
      "description": "<description>",
      "quantity": "<quantity>",
      "unit_price": "<unit_price>"
    },
    "name": "add_quote_line_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYesQuantity
quote_idYesThe quote UUID
tax_rateNoTax rate percentage
unit_priceYesUnit price in cents
descriptionYesLine item description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action without any behavioral context. It does not disclose whether the quote total is recalculated, any status restrictions, or error conditions.

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?

A single, direct sentence that earns its place. It is concise and free of fluff, fitting the tool's simple purpose without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description is too terse. It lacks important context about behavior like price recalculation, required quote status, or the relationship to update_quote_line_item, leaving the agent to infer critical usage constraints from the name alone.

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 provides 100% parameter descriptions, so the description does not need to repeat them. It adds no additional parameter meaning beyond what the schema already defines, 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?

The description 'Add a line item to a quote' uses a specific verb and resource, clearly distinguishing it from invoice line item and other quote operations like update_quote_line_item or delete_quote_line_item.

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 when to use the tool—for adding a line item to a quote—but it doesn't explicitly mention alternatives or when not to use it, such as referencing update_quote_line_item for modifications. No exclusions or contextual guidance are provided beyond the verb.

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

Deploy Server

Other Tools