Skip to main content
Glama

Find a US government fax number

find_agency_fax_number
Read-onlyIdempotent

Look up the official fax number for a US government form or office (IRS, Social Security, USCIS, VA and more) from FaxUp's directory. Each number was read on the agency's own .gov page and carries that page's link and the date it was checked. Read-only; sends 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": "find_agency_fax_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat you need to fax or which office, e.g. "IRS Form 2848", "Social Security", "USCIS I-130", "VA records".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's "Read-only; sends nothing" adds only mild reinforcement. The genuinely valuable additions are provenance and result content: each number was read on the agency's own .gov page and the result carries that page's link and the date it was checked, which tells the agent how much to trust and cite the answer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded: the first states the capability and scope, the second states provenance and the read-only guarantee. Nothing is padded or repeated beyond a brief harmless restatement of the read-only trait.

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 one-parameter lookup with no output schema, the description does useful work by describing what each result carries (source page link and verification date). It stops short of saying how misses or ambiguous agency names are handled, which is the remaining gap for a directory lookup.

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% and the single query parameter already documents itself with examples like "IRS Form 2848". The description adds a mild semantic distinction by showing the query may be a form or an office (IRS, Social Security, USCIS, VA), but that largely overlaps the schema's own examples, so 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?

The description names a specific verb and resource ("Look up the official fax number") and narrows the scope to US government forms and offices, listing IRS, Social Security, USCIS and VA as examples. It also names the data source (FaxUp's directory), so an agent can distinguish this from siblings like send_fax or format_fax_number without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent can infer this is the tool for retrieving a government agency fax number, and the domain restriction to US government sources is clear. However, the description never explicitly says when to prefer this over siblings, what to do for non-government fax numbers, or what happens when a lookup fails.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources