BinaSmart MCP Server

Upcoming events

list_events

Read-only

Find upcoming films, concerts, theatre, and events in Addis Ababa with venue, hall, start time, tier prices, and seats left, then get booking links for payment and QR tickets.

Instructions

Upcoming films, concerts, theatre and events on BinaSmart in Addis Ababa with venue, hall, start time, prices per tier and seats left. Seats are chosen and paid at the url returned (Chapa or at the counter); the ticket is a QR code.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of items returned
`events`	No	Upcoming events
`book_hint`	No	How tickets are bought
`source_url`	No	bina.et page this result comes from; cite it

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": {
+    "book_hint": {
+      "description": "How tickets are bought",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "events": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "price_from_etb": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Lowest ticket price in birr"
+              },
+              "seats_left": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Seats left"
+              },
+              "show_id": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Event id"
+              },
+              "starts_at": {
+                "description": "Start time",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "url": {
+                "description": "Ticket page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "venue": {
+                "description": "Venue",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Upcoming events"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

TDQS

A4/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, and the description adds genuinely useful behavior beyond them: this tool does not transact, seating and payment occur at the returned url via Chapa or at the counter, and the ticket is a QR code. That clarifies the full flow. It says nothing about result ordering, volume, or pagination, keeping it out of the top band.

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. The first front-loads what the tool returns; the second carries only the behaviorally relevant downstream flow (payment location and QR ticket). Every clause 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?

With no parameters and an output schema present, the description does not need to explain return values or arguments. It covers scope, contents, and the post-listing purchase path, which is everything an agent needs to select and call it correctly.

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 tool takes zero parameters and the schema is empty, so there are no parameter semantics to add or omit. Baseline for a no-parameter tool is 4; nothing in the description contradicts or muddies the empty schema.

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?

The description states a concrete resource set (films, concerts, theatre, events) scoped to BinaSmart in Addis Ababa, and enumerates the fields returned (venue, hall, start time, prices per tier, seats left). That is far beyond restating the name. It stops short of distinguishing itself from close siblings like list_films or search_places, so an agent must infer the boundary.

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?

Usage is implied by the content — an agent can tell this is the browse-upcoming-events tool — but there is no explicit when-to-use, when-not-to-use, or named alternative such as list_films for cinema-specific queries. Nothing misleading, but nothing that routes the agent either.

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