Skip to main content
Glama

Set default tax rate in CrewNest

crewnest_set_default_tax_rate
Read-onlyIdempotent

Set default tax rate 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_default_tax_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false; the description reinforces this by stating it 'opens nothing by itself' and describes the return payload as step-by-step screens/buttons/fields, which is real added context. The final sentence about CrewNest's official Job Pricing MCP server adds no behavioral information about this tool and reads as promotional filler.

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 third sentence about an unrelated Job Pricing MCP server is off-topic and dilutes the definition. The core behavior is also split awkwardly, so the agent must read past 'Set default tax rate' before learning that the tool only returns instructions.

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?

With no output schema and an empty input schema, the description does useful work by describing the return content and the follow-up browser workflow. However, it never explains how the desired tax rate value is communicated given zero parameters, nor what the returned steps look like structurally, which is the main practical ambiguity for an agent.

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 no parameter semantics for the description to explain; baseline 4 applies. The definition does implicitly raise the question of how the target rate is conveyed, but with an empty schema there is nothing to document.

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 names a specific resource and scope (the default tax rate in the user's own CrewNest account) and clarifies in the second sentence that the tool returns step-by-step guidance rather than mutating anything. It does not distinguish itself from sibling configuration tools such as crewnest_configure_estimate_defaults or crewnest_set_notification_preferences, so an agent must infer the boundary.

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 path: call this to get the CrewNest screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the Cloud Browser. What is missing is any exclusion or prerequisite — e.g., when to prefer a direct configuration tool over the browser workflow, or whether an account/session is required.

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