BinaSmart

Amharic films to watch online

list_films

Read-only

Licensed Amharic (Ethiopian) films that can be watched online on BinaSmart Watch (bina.et/watch): title in Amharic and English, year, genre, whether it is free or rented for 48 hours (ETB), and the watch url. Free titles are public YouTube releases played through the YouTube player; rentals need Chapa. Optional search by title or genre.

Input Schema

Name	Required	Description	Default
`limit`	No	Max films, default 20
`query`	No	Title (Amharic or English) or genre to filter by; omit for the latest films

Output Schema

Name	Required	Description
`count`	No	Number of items returned
`films`	No	Amharic films
`source_url`	No	bina.et page this result comes from; cite it
`watch_hint`	No	How to watch

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 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"
+      ]
+    },
+    "films": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "free": {
+                "description": "true if free to watch",
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "slug": {
+                "description": "Film slug",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title_am": {
+                "description": "Title in Amharic",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "url": {
+                "description": "Watch page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "year": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Year"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Amharic films"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "watch_hint": {
+      "description": "How to watch",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds real context beyond the readOnlyHint/openWorldHint annotations: free titles are public YouTube releases played through the YouTube player, while rentals require Chapa payment and last 48 hours in ETB. It does not mention ordering, pagination, or result-size behaviour, but the payment/playback distinction is genuinely useful behavioral detail.

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?

Purpose and scope are front-loaded in the first clause, and the sentence carries the field list, the free/rental distinction, and the optional filter without padding. It is a long run-on sentence, but every clause adds information.

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 an output schema present, the description needn't enumerate return values, yet it usefully clarifies what a film record contains and how playback/payment works. The only gap is ordering/result-window behaviour, which is left to the schema.

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 description coverage is 100%, so both parameters are already documented in the schema; the description only restates the query filter ('search by title or genre') and says nothing about limit. Baseline 3 applies when the schema does the heavy lifting.

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+resource (licensed Amharic films watchable online on BinaSmart Watch) and enumerates the returned fields, so an agent can immediately distinguish it from every sibling (news, tenders, rides, hotels, etc.). There is no near-duplicate tool it could be confused with.

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?

Explicitly says search by title or genre is optional, which tells the agent both the filtered and the unfiltered ('latest films') modes. However, it never frames when to use this tool versus any alternative path, and there is no explicit exclusion.

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

All BinaSmart tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.