Skip to main content
Glama

Configure referral rewards in CrewNest

crewnest_configure_referral_rewards
Read-onlyIdempotent

Configure referral rewards 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_configure_referral_rewards"
  }
}

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 and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself' — no contradiction. It adds genuinely useful context beyond the annotations: the return value is a step-by-step walkthrough of screens, buttons and fields, and a separate browser tool family is required to actually apply changes. It stops short of describing failure modes, such as what happens if referral features are not enabled or the user is not signed in.

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 guidance is front-loaded and efficient, but the trailing sentence about CrewNest's official Job Pricing MCP server is promotional, unrelated to selecting or invoking this tool, and dilutes the definition. Removing it would make the description tighter and less likely to distract an agent.

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 it returns (steps, screens, buttons, fields), what it does not do (no changes), and what to do next. Missing only edge-case behavior, which is minor at this complexity.

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 nothing for the description to disambiguate. The description's mention of 'the user's own CrewNest account' supplies the only implicit input (the authenticated account context), which is adequate.

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 opening sentence names a specific resource (referral rewards) and target account, and the second sentence clarifies the actual operation: it returns step-by-step guidance rather than performing the change. The 'configure' verb in the name is slightly misleading given 'opens nothing by itself', but the description corrects that immediately. It distinguishes itself from the cotlet_browser_* family, though it does not differentiate itself from sibling configure_* tools.

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?

The description gives a clear workflow: call this to get the steps, then execute them with the cotlet_browser_* tools in the Cloud Browser. It states the implied context (user's own CrewNest account) without explicit exclusions or a direct comparison to sibling configure_* tools such as configure_estimate_defaults or configure_invoice_reminders.

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