Skip to main content
Glama

Set notification preferences in CrewNest

crewnest_set_notification_preferences
Read-onlyIdempotent

Set notification preferences 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_set_notification_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, and the description adds the non-obvious behavioral fact that explains why: the tool only returns instructions and performs no mutation, deferring the actual write to cotlet_browser_* tools. It stops short of describing scope (which notification preferences exist) or any auth/session requirement for the follow-up browser call.

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 useful, but the final sentence about CrewNest's official free Job Pricing MCP server and its three read-only tools is unrelated marketing that does not help an agent invoke this notification tool. It is stray context that 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-destructive tool whose annotations already carry the safety profile, the description covers the essentials: what comes back (step-by-step screens, buttons, fields) and what must happen next. It would be stronger with a note on what happens if the user is not signed in or which preferences are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline of 4 applies by the stated rule; however, the description adds nothing about how the target account or preference category is determined when no arguments are available, leaving the caller to infer that context comes from the browser session. That small ambiguity keeps it below the zero-parameter baseline.

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?

Names a concrete verb and resource ('Set notification preferences in the user's own CrewNest account') and then corrects the naive reading by stating it 'Returns how to do it in CrewNest step by step (screens, buttons, fields)'. The nature of the tool (a guide generator, not a mutator) is therefore clear, but nothing in the text distinguishes it from the many other crewnest_set_*/configure_* siblings.

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

Usage Guidelines3/5

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

It gives workflow routing – get the steps here, then execute with the cotlet_browser_* tools – and explicitly says it 'opens nothing by itself', which is real when-to-use guidance. But there is no guidance on when to pick this over the sibling configuration tools, or on prerequisites such as an authenticated Cloud Browser session.

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