Fax.Plus

Get fax confirmation report

get-fax-report

Read-onlyIdempotent

Return a short-lived URL for the fax confirmation report (PDF). Save that URL to a file on disk immediately. Do not paste the report bytes into the conversation. Open the saved PDF when the user wants to view it.

Side effects: none (read-only); returns url and expiration_seconds, not file bytes.

Input Schema

Name	Required	Description	Default
`fax_id`	Yes	Fax record ID.
`user_id`	No	Fax.Plus user ID. Default: self.

Output Schema

Name	Required	Description	Default
`url`	Yes
`expiration_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

removedOutput schema / properties / content_type
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / data_base64
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / expiration_seconds
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "content_type",
-  "data_base64"
-]New value: +[
+  "expiration_seconds",
+  "url"
+]

First observedSep 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds real value by disclosing that the URL is short-lived and that the result is a URL plus expiration_seconds rather than file bytes. 'Side effects: none (read-only)' is redundant with the annotations, which keeps this from a 5.

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?

Front-loaded with the core fact (URL for the PDF), followed by compact handling instructions; no rambling. The explicit 'Side effects: none (read-only)' line restates annotations and is the only sentence that doesn't fully earn its place.

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?

For a two-parameter read tool with full schema coverage, an output schema, and annotations covering safety, the description supplies exactly the missing context: the return type (URL, not bytes), its short lifetime, and the required handling. Nothing needed to call or use it correctly is absent.

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 fax_id and user_id (with its 'default: self') are already documented. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Return a short-lived URL for the fax confirmation report (PDF)') and immediately clarifies the return artifact, which separates it from siblings like get-fax or get-file that return metadata or bytes. An agent can tell what this tool yields without opening the schema.

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?

Explicitly tells the agent to save the URL to disk immediately, avoid pasting report bytes into the conversation, and open the PDF only when the user wants to view it — clear operational usage. It lacks an explicit comparison to alternatives (e.g., get-fax for metadata vs. this tool for the confirmation report), so it falls short of a 5.

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

All Fax.Plus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?