Skip to main content
Glama

Send a quote request to the sales team

request_quote

Send a quote or contact request to IP Computers' sales team, who reply by phone or email on business days. Call only after the person explicitly agreed to share their name, email and phone. Sends one email to the sales team; it does not create an order or charge anything.

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": {
      "name": "<name>",
      "email": "<email>",
      "phone": "<phone>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person asking.
emailYesEmail address for the reply.
itemsNoOptional basket to attach, same shape as build_quote items.
phoneYesPhone number, for example 050-0000000.
companyNoBusiness name, optional.
messageNoWhat is needed: products, number of computers or users, questions.

Output Schema

NameRequiredDescriptionDefault
sentYes
emailNo
phoneNo
reply_byNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds substantive behavior: exactly one email is sent to the sales team, the reply arrives by phone or email on business days, and no order is created or charge made. The consent prerequisite is a behavioral constraint not encoded in the schema at all.

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?

Three tight sentences: the action first, the consent gate second, the side-effect disclaimer last. Every sentence carries information the agent would otherwise have to guess, and nothing is repeated from the schema or annotations.

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?

With an output schema present, return values need not be explained, and the description covers the consent gate, the delivery channel, and the no-order/no-charge guarantee — everything needed to call it safely. It could be slightly more complete by noting what the optional 'items' basket does relative to build_quote, but no essential calling information is missing.

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%, so all six parameters are already documented with constraints and examples, making the baseline 3 appropriate. The description only echoes the required name/email/phone in the consent sentence and says nothing extra about the optional 'items' basket or how 'message' shapes the request, so it adds little meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: 'Send a quote or contact request to IP Computers' sales team', with a clear boundary that it 'does not create an order or charge anything'. It does not, however, name the sibling build_quote or explain how a quote request differs from building a quote, so the agent must infer that differentiation.

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?

'Call only after the person explicitly agreed to share their name, email and phone' is an explicit, actionable precondition that tells the agent exactly when the tool may be invoked. The gap is the absence of a when-not/alternative clause pointing to build_quote or get_contact_info for related needs.

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