PromptFax

Get fax status

get_status

Read-onlyIdempotent

Use this when you need the latest PromptFax workflow state, quote/payment state, or fax transmission status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sessionId`	No	PromptFax MCP session identifier returned by start_session. Use this to continue a session-backed fax workflow.
`sendIntentId`	No	PromptFax send intent identifier returned by get_quote or session status. Use this for checkout, send, status, retry, or cancel operations.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds value by specifying the nature of the status (workflow, quote/payment, transmission), which supplements the annotations without contradiction.

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?

Single sentence, front-loaded with purpose, no extraneous words – highly efficient.

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?

With annotations and output schema present, the description explains what the tool returns, and parameters are fully documented in schema. No gaps identified.

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%, and the description adds no new parameter information beyond what the schema already provides. Baseline 3 is appropriate.

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 returns 'latest PromptFax workflow state, quote/payment state, or fax transmission status,' using a specific verb and resource, and distinguishes it from siblings by specifying what status information is provided.

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 explicitly says 'Use this when you need...' which provides usage context. It does not mention when not to use or contrast with sibling tools, but the sibling list and context signals imply alternatives.

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?