Skip to main content
Glama

Update business settings in CrewNest

crewnest_update_business_settings
Read-onlyIdempotent

Update business settings 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_update_business_settings"
  }
}

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?

Annotations declare readOnlyHint=true and the description is consistent with that: it explicitly says the tool 'opens nothing by itself' and returns screens/buttons/fields guidance, which prevents an agent from assuming a mutation occurs. It also names the browser tools to chain into. It does not describe result structure or failure modes, but the safety behavior is well disclosed.

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 each carries useful routing information. The third sentence about CrewNest's separate Job Pricing MCP server and read-only benchmark tools is unrelated to invoking this tool and is pure noise that dilutes the signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 guidance tool with no output schema, the description covers what it returns and what to do next. It still leaves the scope of 'business settings' undefined against a large catalog of narrowly named configure_* and update_* siblings, which is the key ambiguity an agent faces.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed beyond the implicit target account.

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 specific verb and resource (update business settings) and, in the second sentence, reveals the actual mechanics: it returns step-by-step CrewNest instructions rather than performing the change. That redefinition is clear, though it never scopes which settings count as 'business settings' versus the many 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?

Gives a follow-up path ('do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which implies when this tool is appropriate. However, it offers no exclusions or comparison to siblings like crewnest_configure_estimate_defaults or crewnest_configure_online_booking, so an agent must guess whether a specific setting belongs here.

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