Skip to main content
Glama

Manage team member in CrewNest

crewnest_manage_team_member
Read-onlyIdempotent

Manage team member 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_manage_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Strong disclosure beyond annotations: it explicitly states the tool opens nothing itself and only returns step-by-step screens/buttons/fields, and that a separate browser tool family performs the action. That is meaningful context given readOnlyHint=true, confirming the tool is purely instructional. The closing sentence about CrewNest's official Job Pricing MCP server is unrelated and adds no behavioral insight.

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 sentences are front-loaded and useful — what it returns, that it changes nothing, and which tools follow. The final sentence about the official Job Pricing API server is an off-topic tangent that doesn't help an agent decide or invoke, diluting an otherwise tight description.

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?

With no output schema, the description correctly explains the return shape (step-by-step instructions with screens, buttons, fields) and the handoff to browser tools. What's missing is the set of team-member operations covered and any prerequisite about the user being signed into their own CrewNest account, which matters for an instructional tool.

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?

There are zero parameters, so the baseline is 4. Nothing about parameters needs explaining, and the description implicitly frames the call as taking no arguments.

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 verb is 'manage', which is generic for a team member resource — it doesn't say what management actions are covered (role change, permissions, deactivation). The description does clarify the mechanism ('returns how to do it step by step'), but the actual scope of operations remains ambiguous alongside siblings like crewnest_invite_team_member and crewnest_remove_team_member.

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 gives a clear two-step usage pattern: this tool returns instructions, then you execute them with cotlet_browser_* tools in the Cloud Browser. However, it never says when to pick this over the specific invite/remove/regenerate siblings, so routing between the team-member tools still requires 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