Skip to main content
Glama

quaderno

by io.usefulapi

Create a contact

create_contact
Destructive

MUTATES Quaderno data — create a contact (customer or vendor). Provide kind plus a name; use fields for any other Quaderno contact attribute (phone_1, region, postal_code, city, street_line_1/2, tax_status, language, discount, notes, processor/processor_id). Quaderno API: POST /contacts. Returns the created contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesContact kind.
emailNoContact email address.
fieldsNoAdditional raw Quaderno fields merged into the request body (escape hatch for any field not typed above).
tax_idNoThe contact's tax ID / VAT number.
countryNo2-letter ISO country code.
last_nameNoThe person's last name (persons only).
first_nameNoFor a person: their first name. For a company: the company name (Quaderno stores it here).
contact_nameNoThe contact person's name at a company (companies only).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true already signaling mutation, the description reinforces this with 'MUTATES Quaderno data,' specifies the endpoint (POST /contacts), and states that it returns the created contact. It adds useful context without contradicting the annotation.

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?

The description is compact and front-loaded: purpose first, then required/optional inputs, the escape-hatch mechanism, the endpoint, and the return value. Every sentence contributes useful information with no filler.

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 mutation tool with no output schema, it covers creation, required inputs, optional attributes, endpoint, and return value. The main gap is that 'customer or vendor' is not explicitly tied to a schema field or explained via `fields`, leaving some ambiguity about how to express that contact role.

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 the baseline is 3. The description adds meaningful guidance: it tells the agent to provide 'kind plus a name' and explains that `fields` is an escape hatch for additional Quaderno attributes, listing concrete examples such as phone_1, region, and postal_code.

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 specifies a concrete verb and resource: 'create a contact,' with the added detail that the contact is a customer or vendor. This differentiates it clearly from sibling creation tools like create_invoice, create_item, and create_transaction.

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 says to create a contact and outlines core inputs, but it does not explicitly say when to prefer this over update_contact, get_contact, or list_contacts. Usage is implied rather than articulated as a clear decision rule or set of exclusions.

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

All quaderno toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools target distinct resources and actions, but create_invoice and create_transaction both generate tax-compliant sale documents, making their boundary unclear. calculate_tax also overlaps conceptually with the tax calculation embedded in create_transaction, though the descriptions help separate the read-only case.

Naming Consistency4/5

The set follows a consistent verb_noun pattern across get_, list_, create_, and update_ tools, with clear singular/plural usage. calculate_tax and ping fit the style, but quaderno_request is a generic escape hatch that breaks the predictable naming convention.

Tool Count3/5

At 23 tools, the server is on the heavy side and falls in the 16-25 range that feels less scoped than ideal. However, the count is somewhat justified by the many distinct entity types covered, including contacts, invoices, items, credit notes, expenses, receipts, jurisdictions, and webhooks.

Completeness3/5

Core workflows like calculating tax, creating invoices/transactions, and managing contacts/items are covered, and every exposed resource has get/list access. Missing update/delete operations for most resources, read-only webhooks, and no direct creation paths for expenses/receipts/credit notes leave notable lifecycle gaps.

Resources