Skip to main content
Glama

Latest news

muhabbit_news
Read-only

Latest approved news across crypto, finance and tech, from outlets in seven languages, translated to English. Agent-shaped items: signal (the English headline), tokens[], narrative_id, short/long context, sentiment_value. Filter by vertical, topic, tokens or time. (Paid route: API key, wallet token, or x402 payment.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "muhabbit_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
tokensNoComma-separated tickers, crypto or equities, e.g. BTC,ETH or AAPL
categoryNoTopic slug from muhabbit_categories
languageNo
verticalNo
min_importanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tokens / description
      Previous value: -"Comma-separated symbols, e.g. BTC,ETH"New value: +"Comma-separated tickers, crypto or equities, e.g. BTC,ETH or AAPL"
  2. Changed1 schema field changed
    • changedInput schema / properties / vertical / enum
      Previous value: -[
      -  "crypto",
      -  "finance",
      -  "tech",
      -  "turkish"
      -]New value: +[
      +  "crypto",
      +  "finance",
      +  "tech"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile needs no repetition, and the description instead adds genuinely new behavior: items are 'approved' (moderated), translated to English, and the route is paid via API key, wallet token, or x402 payment. That payment/auth disclosure is exactly the kind of context an agent needs before calling. It stops short of explaining rate limits, pagination, or ordering.

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?

One dense paragraph with the resource, source scope, item shape, filtering, and payment model each stated once in that order. Telegraphic phrasing ('Agent-shaped items:') costs nothing and no sentence is redundant.

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 no output schema, the description usefully names the returned fields (signal, tokens[], narrative_id, short/long context, sentiment_value), which is what an agent needs to decide this tool answers its question. It leaves default result count, ordering, and the meaning of 'approved' or min_importance unspecified, but the core is covered.

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 only 29%, so the description must compensate, and it partially does by naming the four filter axes (vertical, topic, tokens, time) that map to vertical, category, tokens, and since. The remaining parameters (limit, language, min_importance) get no explanation, and the 'seven languages' phrasing sits awkwardly against a language enum of only en/tr.

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 gives a specific verb-and-resource ('Latest approved news') plus source scope (crypto/finance/tech, seven-language outlets, translated to English), which is far more than a restatement of the title. It does not name a sibling to contrast with, so an agent must infer that muhabbit_search is the query-driven alternative rather than the recency feed.

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?

'Filter by vertical, topic, tokens or time' implies the browse/filter use case, and the recency framing hints at a feed rather than a search. However, it never states when to prefer this over muhabbit_search, muhabbit_events, or muhabbit_ticker_summary, and there are no exclusions.

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