gryzzly-mcp

create_customer

Creates a customer for billing and project attachment, accepting managers by name, email, or ID. Use before adding projects; check existing customers first to avoid duplicates.

Instructions

Create a customer, the organisation projects are attached to and billed for. Managers can be given by name, email or id. Use it before create_project when the customer does not exist yet; check list_customers first, since a second call creates a duplicate. Returns the new customer with its id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	The customer's name.
`managers`	No	The managers, by name, email or id.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The customer's identifier.
`name`	No	The customer's name.
`managers`	No	The users managing this customer.
`is_active`	No	Whether the customer is active.
`created_at`	No	When the customer was created.
`updated_at`	No	When the customer was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds real value by warning that a second call creates a duplicate, which directly reinforces the non-idempotent semantics. It omits auth/permission requirements, which keeps it short of a 5.

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?

Front-loads the core action, then layers domain role, a parameter hint, ordering guidance, and the duplicate warning. Every sentence carries a distinct piece of information with no filler.

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 2-param create tool with full schema coverage and an output schema, the description covers the creation semantics, prerequisite ordering, duplicate risk, and the return value. Nothing an agent needs to invoke it correctly is missing.

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 both parameters are already documented, including that managers may be given by name, email or id. The description restates this manager guidance rather than adding format or constraint detail beyond the schema, so baseline 3 applies.

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+resource ("Create a customer") and immediately clarifies its domain role (the entity that organisation projects are attached to and billed for). This lets an agent distinguish it from the many create_* siblings without opening the 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?

Gives explicit ordering guidance (use before create_project when the customer doesn't exist) and a concrete precondition plus alternative (check list_customers first to avoid duplicates). Both the when-to-use and the sibling to consult are spelled out.

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