Skip to main content
Glama

Generate referral code in CrewNest

crewnest_generate_referral_code
Read-onlyIdempotent

Generate referral code 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_generate_referral_code"
  }
}

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, openWorldHint=false and destructiveHint=false, and the description reinforces this by stating it opens nothing by itself and returns screens/buttons/fields instructions. That reconciles the potentially misleading 'generate' verb with the read-only annotation rather than contradicting it. It does not describe the shape or length of the returned instructions, which keeps it below a 5.

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 first two sentences are front-loaded and earn their place, but the closing sentence about CrewNest's official Job Pricing MCP server and its read-only benchmark tools has no bearing on generating a referral code. That promotional aside dilutes an otherwise tight definition.

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?

For a zero-parameter, non-mutating tool with full annotation coverage and no output schema, the description supplies what an agent needs: that the return value is procedural guidance and that execution happens via browser tools. The only real omission is routing guidance against crewnest_get_referral_code.

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 baseline score applies and there is no parameter meaning for the description to add. Nothing in the text misleads about inputs.

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 states a specific verb and resource (generate referral code in the user's CrewNest account) and importantly clarifies that the tool itself returns step-by-step instructions rather than performing the action. What it does not do is distinguish itself from the sibling crewnest_get_referral_code, so an agent cannot tell from the text alone which of the two to pick.

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 gives a clear usage pattern: call this to obtain the how-to, then execute it with the cotlet_browser_* tools in the CrewNest Cloud Browser, noting that it 'opens nothing by itself.' That is actionable sequencing guidance. The gap is a lack of explicit exclusion criteria versus crewnest_get_referral_code.

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