Skip to main content
Glama

Compare FaxUp with other fax services

compare_fax_services
Read-onlyIdempotent

How FaxUp's pay-per-fax price compares with other fax apps and services (eFax, iFax, FAX.PLUS, Fax Burner and more): pricing model, App Store rating, and links to side-by-side pages. Prices were read on each service's own site / the App Store; quoted as-is. Read-only.

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": "compare_fax_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceNoOptional: a service name to focus on, e.g. "eFax" or "iFax". Omit to compare all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: it discloses data provenance ('prices were read on each service's own site / the App Store') and the 'quoted as-is' caveat warning that figures may be stale or unsynced. The trailing 'Read-only' merely repeats the annotation but the provenance disclosure is substantive.

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?

One front-loaded sentence leads with the core comparison, then parenthesizes the covered services and the data provenance. Dense but every clause carries information; the vendor list is slightly long but serves to bound scope.

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 read-only lookup with no output schema, the description covers purpose, data provenance, and the content of results (pricing model, rating, links), which is what an agent needs. Only the relationship to the sibling price-quote tool is left unaddressed.

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?

With 100% schema description coverage and a single optional 'service' parameter, the schema already documents the field and its 'omit to compare all' behavior. The description adds no example values or matching semantics beyond what the schema states, so the baseline of 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 concrete verb and resource ('How FaxUp's pay-per-fax price compares with other fax apps and services') and enumerates the compared dimensions: pricing model, App Store rating, and side-by-side links. An agent knows exactly what content comes back, though it does not explicitly contrast itself with the nearby sibling get_price_quote.

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 by the phrasing 'compares with other fax apps' — a reader infers this is for competitive/price comparison rather than quoting FaxUp's own price. There is no explicit when-to-use, no when-not-to-use, and no pointer to get_price_quote as the alternative for single-service pricing.

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