Skip to main content
Glama

Recap

muhabbit_recap
Read-only

Scheduled 1h / 24h / 7d recap for a vertical or all verticals (English). Returns freshness; never generated on demand. (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_recap"
  }
}

Input Schema

NameRequiredDescriptionDefault
verticalNo
timeframeNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description adds substantive behaviour: results are pre-generated on a schedule rather than computed per request, a freshness indicator is returned, output is English-only, and the route is paid via API key, wallet token, or x402. The authentication/payment requirement is exactly the kind of context annotations cannot carry. It stops short of saying what happens on an unpaid or unauthorized call.

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?

Three short sentences, front-loaded with the core scope then the scheduling constraint then the payment caveat, with no filler. The final parenthetical is dense but the density buys real information, so nothing is wasted.

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?

For a two-parameter read-only tool with annotations covering the safety profile, most of what an agent needs is present: scope, cadence, language, freshness, and payment. What is missing is what a recap actually contains (headlines, narratives, sentiment?) and its rough size or structure, which matters because there is no output schema to fall back on.

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 0%, so the description carries the burden. It does enumerate the timeframe values (1h/24h/7d) and explain that 'vertical' accepts a single vertical or 'all', which recovers most of the meaning. It does not cover the concrete vertical enum values or what happens when either optional parameter is omitted, leaving the defaults undocumented in both places.

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 specific resource and scope: a scheduled 1h/24h/7d recap for one vertical or all verticals, in English. That is concrete enough to distinguish it from list-style siblings, but it never names or contrasts itself with near neighbours like muhabbit_news, muhabbit_narratives or muhabbit_ticker_summary, so the 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?

The phrase 'never generated on demand' is a genuine when-not constraint and the word 'Scheduled' signals pre-computed content, which is useful routing information. However, no alternative is named for the case where the agent or user wants fresh/ad-hoc content, so the agent is left to guess which sibling to fall back to.

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