Skip to main content
Glama

Ticker summary

muhabbit_ticker_summary
Read-only

24h AI summary of news about one asset symbol (exists for the most-mentioned assets). (Paid route: API key, wallet token, or x402 payment.)

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": {
      "symbol": "<symbol>"
    },
    "name": "muhabbit_ticker_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / symbol / pattern
      Previous value: -"^[A-Za-z0-9.\\-]{1,20}$"New value: +"^[A-Za-z0-9.-]{1,20}$"
  2. First observed

TDQS

A3.7/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 new behavioral context: the route is paid and requires an API key, wallet token, or x402 payment, which an agent must know before calling. It does not state rate limits or what happens on payment failure, so not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, front-loaded with the core purpose, with no filler. The stacked parentheticals for coverage and payment are slightly dense but each carries information an agent needs.

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?

For a one-parameter read tool with no output schema, the description conveys what is returned (a 24h AI news summary), the coverage limitation, and the payment requirement. Return shape and failure modes are left implicit, which is the main remaining gap.

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 must carry the parameter meaning. It does clarify that the single parameter is an asset symbol and that coverage is limited to popular assets, but it adds no format, casing, or example guidance beyond the schema's regex pattern.

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?

States a specific verb+resource: a 24h AI-generated news summary for a single asset symbol. That distinguishes it from the sibling news/search tools by time window and synthesis. It does not name the specific sibling to prefer for raw news, so it falls short of a 5.

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 parenthetical 'exists for the most-mentioned assets' is a useful pre-condition that tells the agent this call may fail or return nothing for obscure tickers. There is no explicit routing guidance against muhabbit_news, muhabbit_search, or muhabbit_asset_sentiment, so when-to-use versus alternatives is only implied.

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