PromptFax

Get fax quote

get_quote

Fallback/non-widget tool for creating a user-reviewable pay-per-use fax quote when you have a fax number and either an MCP session, a PromptFax documentId, or one or more HTTPS PDF URLs. A quote is required before Stripe Checkout and before any real fax transmission. In ChatGPT widget sessions, do not call this after start_session because the widget auto-quotes once the document and destination are ready.

Input Schema

TableJSON Schema

Name	Required	Description
`fileUrls`	No	One or more HTTPS URLs for PDF or image documents that PromptFax should attach to the fax workflow.
`faxNumber`	No	Destination US fax number. Accepts common human formats such as 415-555-0182 or E.164 format such as +14155550182.
`sessionId`	No	PromptFax MCP session identifier returned by start_session. Use this to continue a session-backed fax workflow.
`documentId`	No	PromptFax document identifier created by a prior upload or hosted session.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.7/5.0

Behavior4/5

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

Annotations (openWorldHint, destructiveHint false) are already present. Description adds context: the quote is user-reviewable, required before Stripe Checkout, and warns against calling after start_session in widget sessions. No contradictions.

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, front-loaded with critical information. No filler; every word serves a purpose. The structure is efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (per context signals), the description adequately covers purpose, prerequisites, usage context, and a key caveat. It is sufficiently complete for an AI agent to correctly invoke the tool.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for each parameter. The description adds value by clarifying that fileUrls expects one or more HTTPS PDF URLs (schema also mentions images) and emphasizes the combination requirement (faxNumber + one of sessionId/documentId/fileUrls).

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

Purpose5/5

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

The description clearly states the tool is a fallback/non-widget for creating a pay-per-use fax quote when you have a fax number and one of sessionId, documentId, or fileUrls. It distinguishes from the widget's auto-quoting mechanism, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides when to use (as a fallback, before checkout/transmission) and when not to use (after start_session in widget sessions). Prerequisites are clearly listed: fax number plus one of the three document sources.

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

All PromptFax tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a distinct purpose: session initiation, document attachment, quoting, payment, sending, canceling, status checking, and retrying failed faxes. No overlap is evident.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., attach_document, get_quote, send_fax), making them predictable and easy to understand.

Tool Count5/5

With 8 tools, the set is well-scoped for a fax-sending service, covering the full lifecycle without being excessive or lacking.

Completeness5/5

The tools cover the entire pay-per-use fax workflow: session start, document attachment, quoting, payment, sending, cancellation, status tracking, and retry. No obvious gaps.

Resources

Need Help?