Skip to main content
Glama

Create customer in CrewNest

crewnest_create_customer
Read-onlyIdempotent

Create customer in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crewnest_create_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them, explicitly stating 'opens nothing by itself.' Beyond the annotations it discloses the actual return content (screens, buttons, fields) and names the external tool family needed to complete the task, which is genuine behavioral value an agent cannot get from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core two sentences are well front-loaded and informative. The closing sentence about CrewNest's official Job Pricing MCP server with three read-only tools is entirely off-topic for creating a customer and adds noise an agent must filter out.

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?

With no parameters and no output schema, the description carries the burden of explaining the return value, and it does so (step-by-step screens, buttons, fields) plus the follow-on action. What is missing is minor: confirmation of authentication/account context and any sibling tool this replaces.

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?

The tool takes zero parameters, so the baseline of 4 would normally apply. However, the description's last sentence diverts into unrelated MCP server promotion rather than using the space to clarify how the tool is invoked or what input (if any) the calling agent should supply. Adequate but not enriched.

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?

Names a specific verb and resource (create customer in the user's CrewNest account) and immediately qualifies it: the tool does not perform the creation, it returns step-by-step instructions for doing it in CrewNest. The opening phrasing ('Create customer...') momentarily suggests a write operation, but the clarifying clause resolves it. It does not distinguish itself from siblings like crewnest_update_customer, though it names the follow-on browser tools.

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?

Gives a clear next-step instruction ('then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which tells the agent this is the guidance phase of a two-phase workflow. It offers no guidance on when to prefer this over sibling create/update operations, and no prerequisites or account requirements are stated.

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.

Resources