Skip to main content
Glama

xero_contacts_create

Create a contact in Xero by supplying the required name and optional information such as email, phone, and tax number.

Instructions

Create a new contact in Xero. Name is required; other fields are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
NameYesContact name (required)
EmailAddressNoContact email address
FirstNameNoContact first name
LastNameNoContact last name
PhoneNoContact phone number
AccountNumberNoAccount number for the contact
TaxNumberNoTax number (ABN in Australia, GST in NZ, VAT in UK)
IsCustomerNoWhether the contact is a customer
IsSupplierNoWhether the contact is a supplier
Behavior2/5

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

No annotations present; the description fails to disclose mutation details, error behavior (e.g., duplicate names), or prerequisites like authentication, leaving the agent underinformed.

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?

Single sentence with no redundancy; action and key requirement are front-loaded, achieving maximum efficiency.

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?

With 9 optional parameters and no output schema or annotations, the description provides minimal context about typical usage, return values, or edge cases.

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%, so baseline 3 applies; the description merely restates the required parameter without adding new meaning beyond 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?

The description clearly states the action (create) and resource (contact in Xero), distinguishing it from sibling read tools like get, list, search.

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?

The description indicates Name is required, but does not explicitly contrast with alternative tools or provide when-to-use guidance beyond the basic action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/xero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server