Skip to main content
Glama

List customers in CrewNest

crewnest_list_customers
Read-onlyIdempotent

List customers 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_list_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's "opens nothing by itself" is consistent with that safety profile. It adds the useful behavioral detail that the result is step-by-step UI guidance meant to be executed via cotlet_browser_* tools, but it never resolves whether actual customer records are returned, leaving the most important behavioral question unanswered.

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 operational content is spread across a long run-on sentence, and the final sentence about CrewNest's 'official, free Job Pricing MCP server with three read-only tools' is unrelated promotional filler that does not help an agent select or invoke this tool. The most decision-relevant fact — that it returns instructions rather than data — is buried mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description is the only source of information about what comes back, yet it is ambiguous about whether customer records, counts, or UI steps are returned. For a tool whose primary value is a list of customers, that gap is significant despite annotations covering the safety profile.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed, though it adds no meaning beyond that.

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

Purpose2/5

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

The title and name say "List customers," but the description says the tool "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself" — so it apparently returns instructions, not customer data. An agent cannot reliably tell whether it will get a customer list or a how-to guide, which is a substantive ambiguity for the tool's core purpose.

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 does route the agent forward: "then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser," which clarifies this is a preparatory step rather than the action itself. However, it gives no guidance against sibling tools (e.g., crewnest_create_customer or other crewnest_list_* tools) and no explicit when-not condition.

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