Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Check robot availability

check_robot_availability
Read-only

Counts delivery robots on duty near a location so you can confirm Serve service availability before quoting a delivery.

Instructions

Count delivery robots on duty near a location. Use this to check whether Serve operates in an area before quoting a delivery.

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": {
      "location": "<location>"
    },
    "name": "check_robot_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes
radius_mNoSearch radius in meters (default 1000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds only that the output is a count and the intent is service-area verification; it says nothing about latency, coverage limits, or what a zero result means. Adequate but thin 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?

Two sentences, zero filler, with the core operation stated first and the usage hint second. Every sentence earns its place.

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 two-parameter tool with a nested address object and no output schema, the definition leaves the radius behavior and the meaning of the returned count unaddressed. The purpose and trigger are complete, but the invocation-relevant details are not.

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

Parameters2/5

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

With schema coverage at 50% and a nested location object, the description needed to compensate. It only says "near a location" and never mentions radius_m, the 1000m default, the 50-50000m bounds, or whether lat/lng can substitute for a full address. The agent must read the schema to learn anything actionable.

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

Purpose4/5

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

States a concrete verb and resource ("Count delivery robots") scoped by proximity ("near a location"), which is clearly distinguishable from siblings like dispatch_robot or track_delivery. It stops short of explicitly naming the alternative it is not, so it lands just under a 5.

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

Usage Guidelines4/5

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

Gives an explicit trigger: "check whether Serve operates in an area before quoting a delivery," which usefully ties it to the get_delivery_quote workflow. No when-not-to-use or exclusions are offered, so it is clear context without full routing guidance.

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