Skip to main content
Glama
bakyang2

kr-crypto-intelligence

get_kr_news_kpop_summary

Read-only

Retrieve AI-analyzed Korean K-pop news: translated articles plus sentiment, key themes, and trending entities. Pay $0.05 per call via x402 micropayment.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of articles to analyze (1-10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds value by specifying a 5-minute cache, pricing details, payment methods, return structure, and that it uses the same articles as get_kr_news_kpop. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description has a clear first sentence but includes detailed pricing/payment bullet points that might be better placed elsewhere. It is functional but could be more concise; every sentence earns its place but the payment info is peripheral.

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?

Given the tool's complexity (AI analysis, multiple return fields) and that an output schema exists, the description covers core functionality, cache, pricing, and return fields. It is sufficiently complete for a single-parameter tool.

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 100% with the only parameter 'limit' described in the schema. The description does not add extra parameter semantics, but baseline is 3 when schema covers parameters. No additional guidance needed.

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 provides Korean K-pop news with an AI analysis layer, listing specific components like overall_sentiment, key_themes, trending_entities, and summary. It explicitly distinguishes itself from the sibling tool get_kr_news_kpop by noting the added AI analysis.

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 description implies usage when AI analysis is desired over raw news, referencing the sibling tool without AI. However, it lacks explicit guidance on when not to use, prerequisites like wallet setup, or alternatives beyond the one sibling.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bakyang2/kr-crypto-intelligence'

If you have feedback or need assistance with the MCP directory API, please join our Discord server