Pocket Drives

Get rental quote

drives_get_quote

Read-onlyIdempotent

Calculate a full rental quote including daily breakdown, taxes, deposit, and total for a date range.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_rental_id": "<asset_rental_id>",
      "date_start": "<date_start>",
      "date_end": "<date_end>"
    },
    "name": "drives_get_quote"
  }
}

Input Schema

Name	Required	Description
`date_end`	Yes	Rental end date (YYYY-MM-DD)
`date_start`	Yes	Rental start date (YYYY-MM-DD)
`asset_rental_id`	Yes	Rental asset ID from search or detail results

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by specifying what the quote includes (daily breakdown, taxes, deposit, total), which is useful behavioral context beyond the annotations.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no unnecessary words. It efficiently communicates the tool's purpose and scope.

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?

For a tool with 3 parameters and no output schema, the description provides a reasonable overview of what is calculated. However, it does not describe the return value format or any edge cases, leaving some gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for all 3 parameters. The description does not repeat parameter details; it focuses on output, which is acceptable since the schema handles parameter semantics adequately.

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 calculates a full rental quote with specific components (daily breakdown, taxes, deposit, total) for a date range. This distinct purpose is well differentiated from sibling tools like search and vehicle detail.

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?

Usage is implied (after selecting a vehicle and dates), but no explicit guidance on when to use vs alternatives, prerequisites, or exclusions is provided. The context of a quote tool is fairly obvious, but the description does not clarify when not to use it.

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

All Pocket Drives tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?