Skip to main content
Glama
dandyer

jobkeepr-mcp

by dandyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a customer

create_customer

Add a new customer record without scheduling a job. For customers with a job, use create_job to handle both at once.

Instructions

Add a new customer without scheduling a job. For new customers WITH a job, use create_job instead — it handles creating the customer inline. Extract ALL contact details the user provides (name, phone, email, address).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCustomer's full name
emailNoEmail address
phoneNoPhone number
sourceNoHow the customer found the business, when the message says so (e.g. a form answer like 'How did you hear about us: Google Search', or 'they found us on Instagram'). Use the account's source name from `jobSources` when one fits. Omit it when the message does not say; never guess.
addressNoAddress
createAnywayNoSet to true ONLY after this tool has reported an existing customer with the same name, phone, or email, and the user answered that they want the new record created regardless. It tells the tool to stop reporting the duplicate and add the customer. Never set it on a first attempt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.2
  2. Removedv1.0.0
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation/non-idempotency profile is covered. The description adds the notable behavioral boundary that no job is created, but is silent on the tool's first-pass behavior of reporting duplicate customers and prompting for createAnyway — a significant trait that lives only inside the parameter schema.

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?

Three short sentences, front-loaded with the core action before the routing rule. No filler, though the final extraction sentence is closer to an instruction than a definition and could be trimmed without loss.

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 6-param create tool with full schema coverage, annotations and no output schema, the description does the important jobs: it disambiguates from create_job and hints at which fields to capture. The duplicate-reporting workflow is delegated entirely to the schema, which is the only real gap.

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 every parameter including the non-obvious createAnyway flow and the source/'never guess' rule is already documented in the schema; baseline 3 applies. The description's 'Extract ALL contact details the user provides (name, phone, email, address)' mildly reinforces which optional fields to populate but adds no syntax or format detail 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?

Specific verb+resource ('Add a new customer') with an explicit scope qualifier ('without scheduling a job') that immediately distinguishes it from create_job, the closest sibling in the tool list. An agent can route to it without opening any 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?

Names the alternative and the exact condition that selects it: 'For new customers WITH a job, use create_job instead — it handles creating the customer inline.' It also instructs what to do with the incoming message (extract all contact details), closing the loop on usage.

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