Skip to main content
Glama

Create supplier

crunch_create_supplier

Creates a supplier in Crunch accounting; only company name is required, with an optional default expense type to speed up future expenses. Check existing suppliers first to avoid duplicates.

Instructions

Create a supplier. Only company_name is required; a default expense_type makes new expenses for this supplier quicker. Check crunch_list_suppliers first to avoid duplicates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>"
    },
    "name": "crunch_create_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
countryNoCountry code, for example GB (see crunch_list_countries)
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
company_nameYesSupplier name, for example Example Supplier Ltd
contact_nameNoContact at the supplier
expense_typeNoDefault expense type for this supplier's expenses, for example TELEPHONE (see crunch_list_expense_types)
vat_registration_numberNoThe supplier's VAT number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the agent knows this is a non-destructive but non-idempotent write. The description adds genuine value by noting the minimal required field and that a default expense_type speeds later expenses, but it never explains duplicate handling, whether the created supplier is returned, or authentication needs.

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?

Three short sentences, front-loaded with the action, then the minimal-input fact, then the duplicate-avoidance rule. There is no redundant restatement and nothing that could be cut without losing information.

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 7-parameter creation tool with one required field, a nested free-form 'extra' object and no output schema, the description covers the essentials an agent needs before calling it: what it creates, the minimum input, and the dedupe pre-check. Missing only failure/duplicate semantics and confirmation of the response shape.

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 every parameter including the nested 'extra' object is already documented in the schema. The description only reinforces 'only company_name is required' and hints at expense_type's defaulting role, which is a modest add over structured data, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Create a supplier') and immediately qualifies scope by naming the only required field. It implicitly separates itself from crunch_update_supplier and crunch_get_supplier by framing the operation as creation, though it never names those siblings explicitly.

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?

It gives a concrete pre-flight rule: 'Check crunch_list_suppliers first to avoid duplicates,' which tells the agent both when and how to use this tool. The gap is that it doesn't state what to do if a duplicate already exists (update instead?) or when creation is inappropriate.

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