Skip to main content
Glama

taxapp.nz

Add a contact

create_contact
Idempotent

Adds a contact: a person or business the organisation deals with, such as a new supplier before adding their bill, a tenant before their tenancy, or a property owner before their property. Give a business's name, or a person's first_name and last_name. Check with list_contacts first that they are not already there: a contact already there with the same name is answered instead, and one without the type asked for is refused: add the type to that contact with update_contact instead. Only for an organisation where this connection may add and change records (list_organisations says which). The answer is the saved contact with its organisation's name.

Input Schema

NameRequiredDescriptionDefault
nameNoA business's name. Leave it out for a person and give first_name and last_name.
emailNoEmail address.
phoneNoPhone number.
mobileNoMobile phone number.
websiteNoWebsite address.
last_nameNoA person's last name.
first_nameNoA person's first name.
contact_typesYesWhat the contact is to the organisation, one or more of: supplier, tenant, contractor, property-owner, landlord or accountant, or a type the organisation added itself (list_choices gives every one with its label).
allow_duplicateNoAdding is safe to repeat: the same details sent again return the record already made. Set true only when the person confirms they really want a second, identical record. For a contact: set true only for a different person or business with the same name.
organisation_idNoThe id of the organisation to use, from list_organisations. Leave it out when the connection covers only one organisation; it is required when it covers more than one.
postal_address_lineNoPostal address, on one line, when it differs from the street address. A contractor or accountant needs a street or postal address.
physical_address_lineNoStreet address, on one line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, but the description adds genuinely non-derivable behavior: a same-name contact is answered rather than duplicated, a contact lacking the requested type is refused, and the return value is the saved contact with its organisation name.

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?

Front-loaded with purpose and examples, but the middle sentences are dense run-ons chained with colons and dashes that require careful parsing. Most sentences carry unique information, so little is wasted, though it could be tightened.

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

Completeness5/5

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

For a 12-parameter creation tool with no output schema, the description supplies the return value, the permission precondition, the duplicate/refusal behavior, and sibling routing. Nothing an agent needs to call it correctly is missing.

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 100%, so baseline is 3, but the description adds the cross-field rule (business name vs person first_name/last_name) and the duplicate-handling semantics for allow_duplicate beyond what the schema field text states. It does not, however, add format constraints for the contact methods or address fields.

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 ('Adds a contact') and immediately characterizes the entity (person or business the organisation deals with) with concrete examples. It distinguishes itself from update_contact and list_contacts by name, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Check with list_contacts first', and the condition that selects update_contact ('add the type to that contact with update_contact instead'). It also states the precondition that the connection must permit adding records, verified via list_organisations.

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.