Skip to main content
Glama

Get referral code in CrewNest

crewnest_get_referral_code
Read-onlyIdempotent

Get 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_get_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 readOnly/idempotent/non-destructive/non-open-world, but the description adds non-obvious behavior: the tool opens nothing by itself and only returns procedural instructions, which must then be executed through the browser tools. That is genuinely useful context an agent could not get from the annotations. The trailing paragraph about CrewNest's official Job Pricing MCP server adds no behavioral value.

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, and the semicolon construction clearly separates 'returns instructions' from 'does not act'. However, the final sentence about CrewNest's official Job Pricing MCP server and its three read-only tools is off-topic promotional content that does not help select or invoke this tool.

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 read-only tool with no output schema, the description covers what comes back (steps, screens, buttons, fields) and what to do next (browser tools), which is what an agent needs. The only completeness gap is the absence of any routing versus `crewnest_generate_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 is 4; there is no parameter meaning for the description to compensate for. The schema is closed (additionalProperties false) and the description correctly implies a parameterless 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 states a specific verb+resource (get the referral code in the user's own CrewNest account) and immediately clarifies the actual deliverable: step-by-step instructions to obtain it, not the code itself. It does not, however, differentiate itself from the sibling `crewnest_generate_referral_code`, leaving the agent to infer that this is the read-only/how-to counterpart of a generating action.

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 workflow: call this to get the screens/buttons/fields, then perform the action with the `cotlet_browser_*` tools in the CrewNest Cloud Browser. It also implies the context (any AI agent, user's own account). What is missing is explicit when-not guidance, particularly versus `crewnest_generate_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