XipFax

Link to add files to a fax

add_fax_file_link

An address where the person adds their pages to their XipFax draft from their own browser, PDFs or photos, with no sign-in there: for a file you can’t reach or pass to add_fax_file, such as one on their phone or one attached to this chat. Give the address to the person alone, since whoever holds it can add pages to their draft. It works once, for 30 minutes. Ask them to add their pages there, press “Done adding pages”, and tell you when they’re done; then call finish_fax_file_link with its link_id.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	Yes	The address to give the person, who opens it in their browser: it needs no sign-in, and works once, for 30 minutes.
`link_id`	Yes	The link, as finish_fax_file_link takes it.
`expires_at`	Yes	When the address stops working, in UTC.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorld=false, idempotent=false), the description discloses the critical behaviors: no sign-in is required at that address, the link is single-use and expires in 30 minutes, and whoever holds it can add pages to the draft. That security constraint is exactly the kind of context annotations cannot encode, and it prevents an agent from broadcasting the link in a group chat.

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?

Length is justified by the workflow, and the order is logical: what the tool gives you, when to use it, the security caveat, the expiry, then the next step. The opening sentence is tangled ('An address where the person adds their pages to their XipFax draft from their own browser, PDFs or photos') and the confidentiality point is stated twice in substance (once as 'no sign-in' and again as 'whoever holds it'), which costs a little density.

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 zero-parameter link-creation tool with an output schema, the description covers everything the caller needs: the reason to choose it over direct upload, the delivery constraint, the lifetime, and the mandatory completion call. No behavioral or sequencing question is left open.

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?

There are no input parameters, so the baseline is 4; the description adds relevant downstream meaning by naming the link_id that finish_fax_file_link later consumes. It does not describe the returned address itself, but an output schema exists, so that is not a gap here.

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?

The description conveys a specific capability: producing an address the end user opens in their own browser to add pages to their XipFax draft, explicitly contrasted with add_fax_file for files the agent cannot reach. The wording leads with 'An address where...' rather than a crisp verb+resource statement like 'creates a one-time upload link', so the agent must infer that this tool generates a link, but the distinction from siblings is unmistakable.

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?

It names the exact condition for use ('for a file you can't reach or pass to add_fax_file, such as one on their phone or one attached to this chat'), effectively excluding it from the normal attach path. It also prescribes the follow-up step: after the user presses 'Done adding pages', call finish_fax_file_link with its link_id, closing the loop to the correct sibling.

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

All XipFax 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?