Skip to main content
Glama

Submit booking request in CrewNest

crewnest_submit_booking_request
Read-onlyIdempotent

Submit booking request 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_submit_booking_request"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces rather than contradicts them by stating it "opens nothing by itself." It adds behavior the annotations cannot express: the return payload is step-by-step UI instructions (screens, buttons, fields) and execution is deferred to a separate browser tool family. It does not cover prerequisites such as an authenticated CrewNest session, which would be the remaining useful detail.

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 operational sentences are front-loaded and earn their place, but the final sentence about CrewNest's official free Job Pricing MCP server and its three read-only tools has no bearing on invoking this tool and reads as promotional filler. Phrasing like 'from ChatGPT, Claude or any AI agent' and the long account-ownership clause add length without reducing ambiguity.

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 parameters, no output schema, and clear safety annotations, the definition covers the essentials and does explain the return shape at a high level. What it leaves out is what an agent needs to actually act: whether a CrewNest Cloud Browser session must already exist, what to do if the cotlet_browser_* tools are unavailable, and how this differs from the sibling review/configure booking tools.

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 with 100% schema coverage, so per the baseline there is nothing for the description to disambiguate. The description does not invent or misdescribe any inputs, which is the correct behavior here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description eventually clarifies that the tool does not submit anything itself but "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." That is a specific and useful statement, but it directly conflicts with the verb in the name/title ('Submit booking request'), so an agent skimming the first clause would misjudge what the tool does. The trailing sentence about CrewNest's official Job Pricing MCP server is unrelated to this tool's purpose and muddies it further.

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 a sequencing hint — get the steps here, then execute with the cotlet_browser_* tools in the CrewNest Cloud Browser — which is real usage guidance. But there is no when-not guidance and no differentiation from plausible siblings like crewnest_review_booking_request or crewnest_configure_online_booking; the agent must infer which booking-related tool fits.

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