Skip to main content
Glama

Search articles

muhabbit_search
Read-only

Full-text search over the article corpus with relevance ranking. (Needs an API key or wallet token: X-API-Key or Authorization: Bearer.)

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": {
      "query": "<query>"
    },
    "name": "muhabbit_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
verticalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / vertical / enum
      Previous value: -[
      -  "crypto",
      -  "finance",
      -  "tech",
      -  "turkish"
      -]New value: +[
      +  "crypto",
      +  "finance",
      +  "tech"
      +]
  2. First observed

TDQS

B3.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 the safety profile is covered; the description adds genuinely non-redundant behavior by naming the exact auth mechanisms (X-API-Key or Bearer wallet token), which affects whether a call can succeed at all. It omits result shape, pagination behavior, and whether ranking is tunable, so it is not exhaustive.

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 short sentences: capability first, prerequisite second. No filler, no restatement of the tool name, and the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should hint at what a result looks like (snippets, scores, article IDs) and how 'limit' interacts with result sets, which it does not. For a three-parameter search tool with a filter enum, coverage is adequate at the headline level but leaves real invocation questions open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description explains none of the three parameters. The 'vertical' enum (crypto/finance/tech) and the 1-50 'limit' bounds are only visible in the raw schema with no semantic explanation, and the 500-character query cap is never mentioned in prose.

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 ('Full-text search over the article corpus') plus a ranking behavior, which is clearly distinct from narrative/sentiment siblings. It stops short of naming any sibling such as muhabbit_news, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no mention of which sibling to pick for browsing versus keyword lookup. Only an auth prerequisite is stated, which is a requirement rather than usage selection guidance.

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