Skip to main content
Glama
mcp-starter-kit

mcp-starter-kit

by 0xJRP

Price a quote

price_quote

Calculates price and total cost from a service name and quantity, helping answer customer questions about how much something costs.

Instructions

Given a service name and quantity, returns the price and a calculated total. Use this when a customer asks how much something costs.

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": {
      "service": "<service>"
    },
    "name": "price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesThe name of the service or product.
quantityNoHow many.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden. It does reveal the return shape (price plus calculated total), which is useful, but says nothing about currency, rounding, or what happens when the service name is unrecognized — meaningful gaps for a pricing tool.

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?

Two sentences, zero filler, with the input/output contract stated first and the usage trigger second. Every sentence earns its place.

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 simple two-parameter read-style tool with no output schema, the definition covers the essential contract: inputs, return values, and when to invoke it. Only edge-case behavior (invalid service, currency assumptions) 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 both parameters are already documented (service name, quantity with default 1 and minimum 1). The description only restates 'service name and quantity' without adding format, matching, or validation detail beyond the schema. Baseline 3 applies.

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?

The description uses a concrete input→output framing: given a service name and quantity, it 'returns the price and a calculated total.' That is a specific verb and resource, clearly distinct from siblings like check_availability or lookup_faq, though it doesn't explicitly contrast itself with them.

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 a clear triggering condition: 'Use this when a customer asks how much something costs.' That is enough to select it over the FAQ or business-info siblings. It stops short of stating when NOT to use it or naming an alternative for edge cases such as unknown services.

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