Skip to main content
Glama
Sign In

kr-crypto-intelligence

by io.github.bakyang2
OverviewDiscussionsAdmin

get_kr_news_kpop_summary

Read-only

Korean K-pop news plus AI synthesis. Same Naver-aggregated, English-translated articles as get_kr_news_kpop, with an added AI analysis layer: overall_sentiment, key_themes, trending_entities (artists/groups), and a paragraph summary. 5-min cache.

💰 Price: $0.05 USDC per call 💳 Payment: x402 micropayment on Base, Polygon, or Solana 🔧 Client: AgentCash, Pay.sh, or any x402 SDK 📖 Docs: https://api.printmoneylab.com/.well-known/x402

Returns: results[] (translated articles) plus ai_analysis with overall_sentiment, key_themes, trending_entities, summary_en.

Args: limit: Number of articles to analyze (1-10, default 5)

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": "get_kr_news_kpop_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of articles to analyze (1-10)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description discloses a 5-min cache, payment via x402, and the AI synthesis behavior. This gives the agent critical operational knowledge without contradicting the annotations.

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?

The description is front-loaded with the core purpose and uses clear sections for returns and args. The payment and docs information adds length but is operationally relevant; not every line is essential but overall it remains well-structured.

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 a single parameter, detailed return structure, and annotations, the description is largely complete. It mentions cache, payment, and output fields, though error handling or rate limits are not addressed.

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?

The input schema fully documents the only parameter, limit, with type, range, default, and description. The description repeats this information but adds no additional semantic meaning beyond the schema.

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?

The description clearly states the tool retrieves Korean K-pop news with an added AI analysis layer. It explicitly distinguishes from get_kr_news_kpop by noting it is the same articles but with additional AI synthesis, making the purpose unambiguous.

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?

The description identifies get_kr_news_kpop as the base alternative and adds an AI analysis layer, implying when to use it for advanced insights. It provides useful context like a 5-min cache and payment requirement, but does not explicitly state when not to use it or list alternative tools.

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

All kr-crypto-intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources