Skip to main content
Glama

Check coverage

check_coverage
Read-onlyIdempotent

Is an address or lat/lng inside a RentADriver service area? covered=true means a delivery can be booked there (in a book-ahead city, RentADriver matches a driver for the scheduled time). Free, no API key.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: the call is free, requires no API key, and the covered=true semantics include the book-ahead scheduling nuance.

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?

Two tight sentences, front-loaded with the core question, followed by the result interpretation and cost/auth note. No wasted wording.

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

Completeness4/5

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

With no output schema, the description does explain the key return field (covered=true) and its meaning. It stops short of describing covered=false or any additional response fields, but is otherwise sufficient for a simple lookup tool.

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 0% and all three parameters are optional, so the description must carry the load. It does clarify that either an address or lat/lng pair is acceptable, but it does not state precedence when both are supplied, required formats, or that at least one input is needed.

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?

Poses a specific question with a clear resource (RentADriver service area) and inputs (address or lat/lng). An agent can immediately tell this is a coverage/eligibility lookup, distinct from siblings like list_service_areas or get_quote.

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?

Implies the pre-booking use case by explaining that covered=true means a delivery can be booked there, and notes the book-ahead city nuance. However, it never explicitly says when to call this versus alternatives (e.g., list_service_areas) or what to do when covered=false.

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.