Skip to main content
Glama
pjosols

pyfastmail-mcp

by pjosols
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

contacts_create_contact

Create a new contact card by providing name, email addresses, phone numbers, organization, and notes, then assign it to one or more address books.

Instructions

Create a new contact card.

Args: name: Full display name of the contact. emails: List of email addresses. phones: List of phone numbers. org: Organization / company name. notes: Free-text notes. address_book_ids: Address book IDs to add the contact to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
emailsNo
phonesNo
orgNo
notesNo
address_book_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.2
    • removedInput schema / properties / address_book_href
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Address Book Href"
-}
    • addedInput schema / properties / address_book_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Address Book Ids"
+}
    • removedInput schema / properties / email
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Email"
-}
    • addedInput schema / properties / emails
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Emails"
+}
    • addedInput schema / properties / name / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / name / default
      Added value: +null
    • removedInput schema / properties / name / type
      Removed value: -"string"
    • removedInput schema / properties / phone
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Phone"
-}
    • addedInput schema / properties / phones
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Phones"
+}
    • removedInput schema / required
      Removed value: -[
-  "name"
-]
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'Create a new contact card' and lists parameters, without describing side effects, validation rules, limits, or what the response contains. The output schema exists but is not referenced.

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

Conciseness3/5

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

The description is concise but the structure is suboptimal: an unformatted list under 'Args' without clear separation. It could be more readable with a list format and clearer headings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given all parameters are optional, the agent needs to know if an empty contact is allowed, or what minimal fields are recommended. No guidance on address_book_ids (e.g., default behavior if omitted). The output schema exists but is not leveraged to explain return data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the description adds minimal meaning beyond the parameter names. For example, 'phones: List of phone numbers' is too vague—no format, constraints, or examples. With 6 optional parameters, richer semantics are needed.

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 clearly states 'Create a new contact card' with a verb and resource. It lists the parameters, which helps understand what fields can be set. However, it does not explicitly differentiate from sibling tools like contacts_update_contact beyond the verb 'create'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no prerequisites or best practices mentioned. The description does not address whether certain parameters are required, or what happens when a contact with the same name or email already exists.

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

Deploy Server

Other Tools