Skip to main content
Glama

Update customer in CrewNest

crewnest_update_customer
Read-onlyIdempotent

Update 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_update_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false, so the safety profile is known. The description reinforces this with "opens nothing by itself" and adds real value by disclosing the output nature (step-by-step screens, buttons, fields), which the agent needs in order to use the result. It stops short of any detail on how those steps are scoped or formatted.

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

Conciseness2/5

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

The operative content is one long, run-on sentence that packs mechanism, output format, and the handoff to browser tools together with a demoted verb. The final sentence about CrewNest's "official, free Job Pricing MCP server" is unrelated promotional filler that does not help an agent select or invoke this tool.

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 zero parameters and no output schema, the description's main burden is explaining what comes back, and it does so (step-by-step screens, buttons, fields) plus what the tool will not do. That is enough for correct invocation, though it omits any bounds on the returned instructions or failure cases.

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?

The tool takes zero parameters, which is the baseline-4 case. Nothing in the description contradicts the empty schema, and the fact that the target customer must be identified some other way (presumably via the browser step instructions) is at least consistent with the parameterless design.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening verb+resource ("Update customer in the user's own CrewNest account") suggests a mutation, but the tool only returns step-by-step instructions; the true purpose is only corrected in the second clause. It names a follow-on path (cotlet_browser_* tools) but never distinguishes itself from siblings like crewnest_create_customer or the other update_* tools. An agent reading only the first sentence would form the wrong model of the tool.

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?

It states the workflow — get steps, then execute via the cotlet_browser_* tools in the user's CrewNest Cloud Browser — which is genuine implied usage guidance. However, it gives no criteria for choosing this over creating a customer, no prerequisites (e.g., does the customer need to exist), and no exclusions. The relationship to the sibling catalog is left entirely to inference.

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