Skip to main content
Glama
Sign In
akembalo-svg

BinaSmart MCP Server

by akembalo-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

BinaSmart Amharic news

list_news
Read-only

Fetch recent BinaSmart news articles by keyword or category, returning headlines, excerpts, and URLs. Find Ethiopian technology, business, law, real estate, and construction stories.

Instructions

Recent articles from BinaSmart news (bina.et/news), mostly in Amharic: technology, business, law, real estate, construction and employment in Ethiopia. Returns the headline, a short excerpt and the url — call get_news_article for the full text.

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles, default 15
queryNoKeyword in the headline or excerpt, English or Amharic. Omit for the newest articles.
categoryNoCategory filter, matched loosely: ቴክኖሎጂ technology, ንግድ business, ሕግ law, ሪል እስቴት real estate, ግንባታ construction, ቅጥር employment, መመሪያ guides.

Output Schema

NameRequiredDescriptionDefault
countNoNumber of items returned
articlesNoAmharic news articles
source_urlNobina.et page this result comes from; cite it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "articles": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "category": {
+                "description": "Category",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "excerpt": {
+                "description": "Excerpt",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "published_at": {
+                "description": "Published",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "slug": {
+                "description": "Article slug for get_news_article",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "description": "Title",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title_am": {
+                "description": "Title in Amharic",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "url": {
+                "description": "Article page",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Amharic news articles"
+    },
+    "count": {
+      "description": "Number of items returned",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.3/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 and locality are covered. The description adds a genuinely useful behavioral trait the annotations cannot convey: content is mostly Amharic. It does not mention pagination or result-ordering behavior, which keeps it short of a 5.

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 with zero filler; the identity and topic scope come first, then the return fields and the hand-off to the sibling. 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 an output schema present, the description need not enumerate return fields in detail, and annotations cover the safety profile. Language, source, topics and the follow-up tool are all present, so nothing an agent needs to call this correctly is missing.

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 limit, query and category are fully documented in the schema, including the loose category matching and the Amharic/English keyword rule. The description's topic list largely restates the category parameter, adding no syntax or semantics beyond the schema. Baseline 3 applies.

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 (list), resource (recent articles) and source (BinaSmart news / bina.et/news), plus the topic coverage. It explicitly contrasts with the sibling get_news_article, so an agent can route between the two without opening either schema.

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?

Clearly implies when to use it (recent articles, browse-level) and names the alternative get_news_article with the condition that selects it (full text). It does not state exclusions versus other list_* siblings, but the usage context is unambiguous.

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

Deploy Server

Other Tools