Skip to main content
Glama

List crew in CrewNest

crewnest_list_crew
Read-onlyIdempotent

List crew 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_crew"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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, so the safety profile is covered. The description adds useful behavioral context ('opens nothing by itself', returns screens/buttons/fields), which is more than the annotations provide, but it does not clarify the actual response structure or how the returned steps should be consumed, and it muddies the picture with a detour about another MCP server.

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 core useful content is the first two sentences, but the trailing 'CrewNest's official API... Job Pricing MCP server with three read-only tools' sentence is irrelevant to invoking this tool and acts as a distractor. Structure is also weak because the 'explanatory guide' nature is buried after a misleading list-style opening.

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

Completeness3/5

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

For a zero-parameter read-only tool with full annotation coverage, the description is roughly adequate: it states it returns step-by-step UI instructions and defers execution to cotlet_browser_* tools. However, the competing 'list crew' framing and the off-topic official-API sentence leave the agent without a clean, confident understanding of what it will actually receive.

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, so the description has nothing to disambiguate and the schema is trivially complete; the baseline of 4 applies. No parameter-level meaning is needed or missing.

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 name and opening clause ('List crew in the user's own CrewNest account') imply it returns crew data, but the next sentence says it 'Returns how to do it in CrewNest step by step (screens, buttons, fields)' and performs nothing itself. That is a materially different behavior than its sibling crewnest_list_* tools, and the description never reconciles the two, leaving the agent unsure whether this is a data-returning list tool or a procedural 'how-to' guide.

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 onward ('then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which is a real usage instruction. But it gives no when-to-use vs the many crewnest_list_* siblings (jobs, invoices, customers, etc.) and no when-not-to-use guidance, so the selection logic is only partially implied.

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