Fax.Plus

Create contact

create-contact

Destructive

Create a new contact in Fax.Plus address book. Requires name and fax_number (E.164, e.g. +15551234567). Optional groups must be group names (e.g. Vendors), not group IDs.

Side effects: creates contact.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Contact name (required).
`email`	No	Optional email.
`notes`	No	Optional notes.
`phone`	No	Optional phone.
`groups`	No	Optional group names (not IDs), e.g. ["Vendors"].
`shared`	No	Optional: share with corporate members.
`cellphone`	No	Optional cellphone.
`fax_number`	Yes	Contact fax number in E.164 form (required), e.g. +15551234567.
`is_telefax`	No	Optional: whether the contact has a human fax operator.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`email`	No
`notes`	No
`phone`	No
`groups`	No
`cellphone`	No
`is_shared`	No
`fax_number`	No
`is_telefax`	No
`creation_date`	No
`modification_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, and the description reinforces the mutation by noting 'Side effects: creates contact.' It does not add much beyond that or provide additional behavioral context such as permissions, idempotency, or duplicate handling, but it does not contradict the annotations.

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?

The description is compact, with the main purpose stated first and constraints following. The 'Side effects: creates contact' line is somewhat redundant with the first sentence, but the overall structure is efficient and easy to scan.

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?

Given the 100% schema coverageinches and the presence of an output schema, the description covers the essential behavioral constraints: required fields, E.164 format, and group-name semantics. It could add when to choose this over update-contact, but that is a minor omission for a straightforward create operation.

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 description coverage is 100%, so the schema already documents all 9 parameters. The description repeats the required fields and E.164/group-name constraints but does not add meaning beyond what the schema provides.

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 opens with 'Create a new contact in Fax.Plus address book' — a specific verb, resource, and service scope. It clearly distinguishes the tool from siblings like update-contact, delete-contact, list-contacts, and create-contact-group.

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?

The description explicitly states required fields (name and fax_number) and important constraints like E.164 format and group names vs IDs. It does not explicitly name update-contact as the alternative for modifying an existing contact, but the use case is unambiguous from 'Create a new contact'.

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

All Fax.Plus 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?