Skip to main content
Glama

Supplier Delivered Quote Comparison

bpj_supplier_delivered_quote_comparison
Read-onlyIdempotent

Compare annual delivered purchasing costs including freight and incremental alternative storage.

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": {
      "annual": "<annual>",
      "standard": "<standard>",
      "discount": "<discount>",
      "freightA": "<freightA>",
      "freightB": "<freightB>",
      "extra": "<extra>"
    },
    "name": "bpj_supplier_delivered_quote_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
extraYes
annualYes
discountYes
freightAYes
freightBYes
standardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the framing that freight and incremental storage are part of the comparison, and says nothing about what is returned (per-quote totals, delta, or a winner). With annotations doing the behavioral work, a 3 is fair but no higher.

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?

A single front-loaded sentence with no filler or restated title-as-prose. It is lean, though the brevity comes partly at the cost of the parameter and output detail noted elsewhere.

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?

This is a six-required-parameter calculator with no output schema, so the description should say what result an agent will receive and how the two quotes are compared. Instead it only restates the inputs at a high level, leaving the return shape and the comparison logic entirely undisclosed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of explaining the six required numerics, and it does not. It never clarifies that the prices are per-unit and get multiplied by annual demand, nor whether freight and storage figures are absolute annual totals or per-unit, nor what currency/unit assumptions apply. The field titles hint at meaning, but the description adds essentially nothing beyond them.

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?

States a specific verb ("Compare") and a specific resource ("annual delivered purchasing costs including freight and incremental alternative storage"). An agent can tell this is a two-quote delivered-cost comparison rather than, say, a fixed-fee quote or an absence-cover cost. It stops short of naming which sibling calculator is the alternative.

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?

Usage is only implied: comparing two supplier quotes where freight and extra storage differ. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling like bpj_fixed_fee_project_quote for other cost shapes. Adequate but leaves the agent to infer the scenario.

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.