Skip to main content
Glama
CSOAI-ORG

Planthire AI MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_rental_quote

Calculate equipment rental pricing with tiered daily, weekly, and monthly rates. Add optional insurance, fuel, and operator costs for a detailed GBP breakdown.

Instructions

Calculate rental pricing for equipment.

Applies tiered pricing: daily rate for 1-6 days, weekly rate for 7-27, monthly rate for 28+. Includes optional insurance, fuel, and operator costs.

Args: equipment_id: ID from search_equipment results. duration_days: Number of hire days. include_insurance: Add damage waiver insurance (default True). include_fuel: Include estimated fuel costs. operator_required: Include CPCS-carded operator.

Returns: Detailed pricing breakdown in GBP.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). 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
api_keyNo
equipment_idYes
include_fuelNo
duration_daysYes
include_insuranceNo
operator_requiredNo

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: read-only, stateless, idempotent, rate limits, authentication, error handling, side effects, and data privacy. This adds significant value beyond the schema.

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

Conciseness4/5

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

The description is well-structured with clear sections (Args, Returns, Behavior, When to use) and front-loaded purpose. However, there is some redundancy (rate limits mentioned in both Behavior and Behavioral Transparency), which slightly reduces conciseness.

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

Completeness5/5

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

Despite no output schema, the description explains returns ('Detailed pricing breakdown in GBP') and covers all necessary aspects: parameters, behavior, error handling, rate limits, and idempotency. It is complete for a complex pricing 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?

Schema description coverage is 0%, so the description compensates well. The 'Args' section explains each parameter's purpose and default values, except for 'api_key' which is omitted. Overall, it adds meaning beyond the schema's type and title.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Calculate rental pricing for equipment.' It details tiered pricing (daily, weekly, monthly) and optional costs (insurance, fuel, operator). This specificity distinguishes it from sibling tools like search_equipment or create_booking.

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

Usage Guidelines5/5

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

The description includes explicit 'When to use' and 'When NOT to use' sections, providing clear guidance. It also contextualizes the equipment_id parameter as coming from search_equipment results, and outlines rate limits and authentication requirements.

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