Skip to main content
Glama

Regenerate team invitation in CrewNest

crewnest_regenerate_team_invitation
Read-onlyIdempotent

Regenerate team invitation 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_regenerate_team_invitation"
  }
}

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces this with "opens nothing by itself." It adds genuine value beyond the annotations by disclosing what the tool actually returns: a step-by-step walkthrough of screens, buttons and fields, plus the follow-up path through browser tools.

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 behavior and follow-up path are stated up front and earn their place. However, the closing sentence about CrewNest's separate Job Pricing MCP server is unrelated promotional filler, and "from ChatGPT, Claude or any AI agent" adds no selection value.

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 a simple guidance-tool scope, the description covers what the agent needs: what is returned, that no UI action occurs here, and which tool family completes the task. Only the when-to-use-this-vs-siblings dimension is left implicit.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly presents this as a zero-argument, no-target-needed call.

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 ("Regenerate team invitation") scoped to the user's own CrewNest account. It also clarifies the tool's actual nature — returning step-by-step instructions rather than performing the action — which distinguishes it from a hypothetical direct-action invite tool, though it does not name any sibling explicitly.

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?

Usage is clear: call this to get screens/buttons/fields, then execute with the cotlet_browser_* tools, because this tool "opens nothing by itself." The one gap is that it never states when to prefer this over sibling tools like crewnest_invite_team_member, though per the rules no omitted alternative is presumed.

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