Skip to main content
Glama

Invite team member in CrewNest

crewnest_invite_team_member
Read-onlyIdempotent

Invite 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_invite_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so safety is covered. The description adds real value beyond them by specifying the return content (screens, buttons, fields) and the key behavioral fact that it 'opens nothing by itself,' which prevents an agent from assuming the invite was actually sent.

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 purpose and execution path are front-loaded in two sentences, but the closing sentence about CrewNest's separate Job Pricing MCP server has no bearing on inviting a team member and dilutes an otherwise tight definition. One of three sentences does not earn its place.

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, no output schema and strong annotations, the description supplies what an agent needs: what it returns, that it performs no action, and which tool family executes the work. An agent could call it correctly after reading once, though the off-topic pricing sentence is mild noise.

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 there is nothing for the description to disambiguate and the baseline is 4. No parameter-level confusion is possible.

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?

The description names a specific verb and resource (invite team member in the user's CrewNest account) and then clarifies the crucial twist that it returns step-by-step instructions rather than performing the invite. That clarification is genuinely useful, though the opening sentence reads at first like a write action, and it does not explicitly distinguish itself from siblings such as crewnest_manage_team_member or crewnest_regenerate_team_invitation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the workflow explicitly: this tool returns the how-to, and the actual execution happens with cotlet_browser_* tools in the user's CrewNest Cloud Browser. That answers 'when do I call this and what do I do with the result.' It stops short of naming sibling tools to avoid, so it earns a 4 rather than a 5.

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