Skip to main content
Glama

Configure online booking in CrewNest

crewnest_configure_online_booking
Read-onlyIdempotent

Configure online booking 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_online_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The description reinforces readOnlyHint by stating the tool 'opens nothing by itself' and discloses the return shape (screens, buttons, fields), which is genuinely useful beyond the annotations. However, the closing sentence about CrewNest's official Job Pricing MCP server is unrelated to this tool and adds no behavioral information about it, diluting rather than deepening transparency.

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?

Guidance and handoff are front-loaded and the core two sentences earn their place. The final sentence about a separate free Job Pricing MCP server is off-topic noise that a reader must discard, and the 'ChatGPT, Claude or any AI agent' phrasing is filler.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so by naming the step-by-step format. It also tells the agent how to complete the task afterward, which is the missing piece for an instructional tool.

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 to explain and the schema coverage is complete by definition. The description correctly avoids inventing inputs and notes the follow-up happens through separate browser tools.

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 first sentence states a specific verb and resource (configure online booking in the user's CrewNest account) and the second clarifies that the tool returns step-by-step guidance rather than performing the action. That correction is valuable because the 'configure' prefix would otherwise suggest a mutation. It does not, however, distinguish itself from the many sibling configure_* tools beyond the booking subject.

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 concrete when-to-use context and an explicit workflow handoff: call this to get the steps, then act with the cotlet_browser_* tools in the Cloud Browser. There is no explicit exclusion or comparison against siblings such as crewnest_review_booking_request or crewnest_configure_estimate_defaults, so it stops short of full routing guidance.

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