Faxette

Block a fax number

block_sender

DestructiveIdempotent

Use this only after the person confirms they want to block a number: future faxes from it to the organization are deleted as they arrive, and nobody is emailed. Pass inbound_fax_id to block the number a received fax came from, or number for a number the person gives you. Faxes already in the inbox stay. unblock_sender undoes it. Needs the person to sign in to Faxette.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organization": "<organization>"
    },
    "name": "block_sender"
  }
}

Input Schema

Name	Required	Description
`number`	No	A fax number the person gave you, in international format, like +12125550100.
`organization`	Yes	The organization's id from get_organizations. Ask the person which one if there are several.
`inbound_fax_id`	No	A received fax from get_inbound_faxes.

Output Schema

Name	Required	Description
`id`	Yes
`number`	Yes	The blocked fax number.
`blocked_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructive/idempotent/not-readOnly, but the description adds real value beyond them: inbound faxes are silently deleted on arrival, no notification email is sent, faxes already in the inbox are preserved, and the person must be signed in to Faxette.

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 confirmation precondition, then effects, then parameter routing, then reversal. Dense but every clause carries information; the two parameter modes could be split for faster scanning.

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?

Covers preconditions, side effects, persistence scope, auth requirement, and the undo path, and an output schema exists so return values need no explanation. Only the mutual-exclusivity of number and inbound_fax_id is left unstated.

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 coverage is 100%, so all three parameters are already documented. The description adds the useful decision rule that inbound_fax_id blocks the sender of a received fax while number handles a person-supplied number, but it does not say what happens if both are provided or how they interact.

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 ('block a number') and immediately defines the effect: future faxes from it are deleted as they arrive. Clearly distinguishable from sibling unblock_sender and from the read-only get_blocked_senders.

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?

Explicit precondition ('Use this only after the person confirms they want to block a number') plus the named inverse tool 'unblock_sender undoes it'. The two ways to identify the target are also given, so the agent knows which path selects which tool behavior.

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

All Faxette 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.