Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Geofence point-in-polygon check

route-optimization_geofence-check
Read-onlyIdempotent

Test points against GeoJSON service zones with holes, reporting inside/in-hole status and nearest boundary distance. Price $0.02 USDC. POST /api/v1/route-optimization/geofence-check. An unpaid call returns the x402 payment terms and does not run.

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": {
      "zones": "<zones>",
      "points": "<points>"
    },
    "name": "route-optimization_geofence-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonesYeszones, object. Required.
pointsYespoints, array. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

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?

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable context beyond those annotations: pricing of $0.02 USDC and the fact that an unpaid call returns x402 payment terms without executing. It does not describe boundary inclusion rules or zone-precedence behavior.

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 four sentences and front-loads the core behavior before endpoint and payment details. Every sentence contributes useful information for an agent deciding whether and how to call the tool.

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?

Given the nested GeoJSON schema, output schema presence, and annotations, the description is largely complete: it explains the core computation, reporting outputs, endpoint, and payment gating. It leaves out subtle geospatial behavior such as boundary point handling and multiple-zone precedence, which prevents a perfect score.

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?

The input schema has 100% description coverage and already documents the zones and points structures in detail. The description adds only light semantic context by noting GeoJSON zones with holes, but does not add parameter-level format or interpretation guidance beyond the schema.

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 states a specific verb and resource: test points against GeoJSON service zones, including holes, and report inside/in-hole status plus nearest boundary distance. This clearly distinguishes the tool from route optimization siblings such as territory clustering or distance matrix operations.

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 by saying it tests points against service zones, but it does not explicitly state when to choose this tool over alternatives or when not to use it. No sibling tool is named as an alternative.

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.

Resources