Skip to main content
Glama
Sign In
nexwave-mcp-remote

nexwave-mcp-remote

by Sidarau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Fleet List

fleet_list
Read-onlyIdempotent

Retrieve the current Sketchy Rides LA fleet list with daily rates, mileage terms, photos, and booking URLs.

Instructions

List the current published Sketchy Rides LA fleet: daily rates, mileage terms, photos, and booking URLs.

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": "fleet_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful context about the contents of the list ('current published... daily rates, mileage terms, photos, booking URLs') but does not disclose behaviors like pagination or all-vs-partial listing beyond what the annotations imply.

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?

A single sentence leads with the verb and resource, then enumerates the relevant data fields. No filler or repetition; every phrase earns its place.

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?

The tool is a simple zero-parameter list with a strong annotation set and an output schema present. The description fully covers what the agent needs to know to invoke it: what resource is listed and what data will be returned.

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 input schema has zero parameters, so there are no parameter semantics to document. The rubric sets a baseline of 4 for a zero-parameter tool, and the description's content coverage makes this appropriate.

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?

Begins with the specific verb 'List' and identifies the exact resource, 'current published Sketchy Rides LA fleet,' plus the data included (daily rates, mileage terms, photos, booking URLs). This distinguishes it from sibling tools like quote_trip or availability_check, which serve different purposes.

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?

The description implies the use case—call this when the agent needs the current published fleet listing—and the 'current published' wording sets scope. However, it does not explicitly state when to choose fleet_list over search, fetch, availability_check, or quote_trip, nor does it list exclusions.

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

Deploy Server

Other Tools