Skip to main content
Glama
Sign In

Faxette

by com.faxette
OverviewDiscussionsAdmin

Unblock a fax number

unblock_sender
Idempotent

Use this when the person wants faxes from a blocked number to reach the organization again. Members are emailed when they arrive. 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>",
      "number": "<number>"
    },
    "name": "unblock_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesThe blocked number, from get_blocked_senders.
organizationYesThe organization's id from get_organizations. Ask the person which one if there are several.

Output Schema

NameRequiredDescriptionDefault
idYes
numberYesThe blocked fax number.
blocked_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-read-only behavior, so the remaining burden is low. The description still adds real context beyond them: a downstream side effect ('Members are emailed when they arrive') and an authentication requirement (sign in to Faxette) that annotations do not express.

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?

Three short sentences, all of which carry information, with the trigger front-loaded. Minor compression cost: 'when they arrive' has an ambiguous antecedent (the faxes, not the members), which a slightly clearer phrasing would avoid.

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?

For a two-parameter mutation with a full output schema, the description covers trigger, side effect, and auth requirement. It leaves unstated what happens if the number was never blocked, though idempotentHint suggests that is safe.

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%, with both parameters documented and even pointing at their source tools (get_blocked_senders, get_organizations). The description adds no additional meaning about the number format or organization selection, so the baseline 3 is appropriate.

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 names a specific action (restoring delivery from a blocked number) and its effect ('faxes from a blocked number to reach the organization again'). This implicitly distinguishes it from the sibling block_sender, but never names that inverse tool explicitly, so the differentiation is left to inference.

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 gives an explicit trigger condition ('Use this when the person wants faxes ... to reach the organization again') and a prerequisite ('Needs the person to sign in to Faxette'). It does not name block_sender as the alternative or say what to do if the number isn't actually blocked, but the usage context is clear.

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

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