Skip to main content
Glama
Sign In

Faxette

by com.faxette
OverviewDiscussionsAdmin

Find a checked fax number

lookup_fax_number
Read-onlyIdempotent

Search Faxette's catalog by agency, form number or purpose. Returns only numbers supported by this connector, with the official source and verification date. An empty result means we have no current match, not that the office has no fax number. Show the source and have the person confirm the right office before creating a fax. It changes nothing.

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": {
      "query": "<query>"
    },
    "name": "lookup_fax_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
destinationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so 'It changes nothing' is redundant, but the description adds genuinely new behavioral context: results carry an official source and verification date, and empty results have a specific non-obvious meaning. It does not discuss rate limits or result ordering, keeping it 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?

Four short sentences, front-loaded with what is searched and what is returned, followed by interpretation and safety guidance. The only wasted clause is 'It changes nothing', which repeats the readOnlyHint annotation.

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?

An output schema exists so return structure needn't be spelled out, yet the description still flags the meaningful return fields (source, verification date) and the empty-result semantics. For a one-parameter read tool this is close to complete; only the interaction with create_fax could be made more explicit.

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?

Schema coverage is 0% and the single `query` parameter has no schema description, so the description carries the burden. It does so by enumerating the accepted search dimensions (agency, form number, purpose), which tells an agent what to put in `query`; it doesn't mention length bounds, but those are visible in the schema.

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 ('Search Faxette's catalog') plus the query axes (agency, form number, purpose), and scopes the result set ('only numbers supported by this connector'). This clearly separates it from the sibling tools, which all deal with sending, retrieving, or reviewing actual faxes rather than looking up verified numbers.

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?

Gives real workflow guidance: show the source and have the person confirm the right office before creating a fax, and warns that an empty result means no current match rather than no fax number existing. It lacks an explicit hand-off to a named alternative (e.g. create_fax), so it stops 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 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