Skip to main content
Glama

Get a fax price quote

get_price_quote
Read-onlyIdempotent

What a fax costs on FaxUp, optionally for a given fax number and page count. Checks the number can be faxed (country served, not a mobile line). Read-only; charges nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoPages in the document, if known.
countryNoISO country code for a number given without "+", e.g. "GB".
to_numberNoFax number in international form, e.g. "+1 202 555 0143" or "+44 20 7123 4567". Without a "+" it is read as US/Canada, or as `country`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' is largely repetition. However 'charges nothing' clarifies the cost consequence, and the statement that the number is validated for country coverage and mobile-line exclusion is genuine behavioral context an agent would not otherwise know.

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 short sentences, front-loaded with the core purpose, then the validation behavior, then the safety/cost note. No redundant or filler wording.

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 zero-required-parameter read-only pricing tool with a fully described schema and no output schema, the definition covers purpose, optional inputs, validation behavior, and cost. It could go slightly further by indicating what the quote response contains (e.g., currency or per-page breakdown), but nothing needed to call it correctly 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 description coverage is 100%, so all three parameters (pages, country, to_number) are already documented with formats and examples. The description restates the number and page-count inputs but adds nothing about them and never mentions the country parameter, so 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?

States a specific resource and outcome: the cost of a fax on FaxUp, with optional scoping by number and page count. It is clearly distinguishable from siblings like send_fax or compare_fax_services, though it never names an alternative explicitly.

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 phrase 'optionally for a given fax number and page count' implies the tool works with or without arguments, and the validation note hints at a pre-send check use case. There is no explicit when-to-use or when-not-to-use guidance versus get_country_fax_guide, compare_fax_services, or format_fax_number.

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