Skip to main content
Glama
CSOAI-ORG

Planthire AI MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

create_booking

Create a booking for equipment hire by specifying equipment ID, dates, depot, customer details, and optional extras like insurance, operator, or delivery.

Instructions

Create an equipment booking.

Args: equipment_id: Equipment ID from catalog. start_date: Hire start date (YYYY-MM-DD). end_date: Hire end date (YYYY-MM-DD). depot: Collection depot. customer_name: Booking contact name. customer_email: Contact email. customer_phone: Contact phone number. include_insurance: Add damage waiver insurance. operator_required: Book with CPCS operator. delivery_address: If provided, equipment will be delivered (extra cost).

Returns: Booking confirmation with reference number.

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results. Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depotNolondon
api_keyNo
end_dateYes
start_dateYes
equipment_idYes
customer_nameNo
customer_emailNo
customer_phoneNo
delivery_addressNo
include_insuranceNo
operator_requiredNo

Tool Definition Quality

D1.8/5.0
Behavior1/5

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

The 'Behavioral Transparency' section claims the tool is read-only with no side effects, directly contradicting the tool's apparent purpose of creating a booking (a write operation). This is a critical inconsistency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly long and includes redundant content (e.g., repeated behavioral info) and irrelevant sections like generic 'When to use' text. It should be concise and focused on booking creation.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 11 parameters and no output schema or annotations, the description fails to coherently explain how to create a booking. The contradictory behavior claims and irrelevant analysis context make it incomplete and unusable.

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 description lists 10 out of 11 parameters with short explanations (e.g., 'equipment_id: Equipment ID from catalog'), adding value beyond the schema's minimal titles. However, the api_key parameter is missing from the description.

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

Purpose2/5

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

The description initially states 'Create an equipment booking' but later includes a 'Behavior' section describing a read-only analysis tool with no side effects, which contradicts the tool's name and purpose. This confusion undermines clarity.

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

Usage Guidelines1/5

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

The 'When to use' and 'When NOT to use' sections describe generic 'structured analysis or classification' use cases that are irrelevant to creating bookings, providing no actual guidance on when to use this booking tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/planthire-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server