BinaSmart MCP Server

Find BinaPool cars filling near a point

find_pool_groups

Read-only

Find carpool groups near a point in Addis Ababa by latitude and longitude. See destination, seats left, price, women-only option, and a join link.

Instructions

Cars currently filling within about 2.5 km of a point in Addis Ababa: destination, seats left, seat price, women-only flag, and a share url (https://bina.et/pool/) the rider can open to join. Driver-opened cars at stations are listed first. Requires lat/lng.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "find_pool_groups"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes	Latitude
`lng`	Yes	Longitude

Output Schema

Name	Required	Description
`note`	No	How to use or present this result
`count`	No	Number of items returned
`groups`	No	Cars filling up near the given point
`start_one_url`	No	Start a new pool group

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "groups": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Cars filling up near the given point"
+    },
+    "note": {
+      "description": "How to use or present this result",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "start_one_url": {
+      "description": "Start a new pool group",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: an approximate 2.5 km search radius and the ordering rule that driver-opened cars at stations come first. It stops short of stating result limits or pagination.

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

Conciseness4/5

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

One dense sentence that front-loads the verb, scope, and radius before listing return fields. The inline share-url template is slightly more detail than needed for tool selection, but nothing is wasted or padded.

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?

An output schema exists, so return-value explanation is optional; the description still summarizes the payload fields helpfully. Combined with the annotation-provided read-only profile and the geographic constraint, an agent has enough to call this correctly.

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% and the bounds (8.5–9.5 lat, 38.4–39.2 lng) already pin the coordinates to Addis Ababa. The description's 'point in Addis Ababa' and 'Requires lat/lng' only restate what the schema conveys, so this is the baseline 3.

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?

States a specific verb (Find) and resource (BinaPool cars currently filling near a point), then enumerates the returned fields. It is clearly distinguishable from siblings like list_pool_corridors, quote_ride, and request_ride.

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 usage via 'Requires lat/lng' and the 2.5 km radius, but never states when to pick this over list_pool_corridors or how it relates to the ride-booking siblings. Usage is inferable rather than explicit.

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