Skip to main content
Glama

search_balanced_news

Search AI-synthesized news stories that aggregate multiple sources with summaries, evidence breakdowns, and potential outcomes.

Instructions

Search Helium's balanced news stories — AI-synthesized articles that aggregate multiple sources.

Unlike search_news (which returns individual RSS articles), this returns Helium's own
synthesized stories: each one draws from multiple sources and includes an AI-written
summary, takeaway, context, evidence breakdown, potential outcomes, and relevant tickers.

Returns a list of stories, each with:
- title, simple_title, date, category
- page_url: full URL to the story on heliumtrades.com
- image: story image URL (when available)
- summary: Helium's synthesized overview
- takeaway: key conclusion
- context: background context
- evidence: numbered evidence items
- potential_outcomes: forward-looking outcomes with probabilities
- relevant_tickers: related stock tickers
- num_sources: number of source articles synthesized
- rank: search relevance score

Args:
    query: Search keywords (required).
    limit: Max results (1-50, default 10).
    category: Filter by category. One of: 'tech', 'politics', 'markets', 'business', 'science'.
    days_back: Only include stories from the last N days. 0 means no date filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
categoryNo
days_backNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by detailing the return format (list of stories with specific fields), search functionality, and filtering capabilities. However, it doesn't mention rate limits, authentication requirements, or error behaviors, leaving some behavioral aspects uncovered.

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?

The description is efficiently structured with purpose statement, sibling differentiation, return format details, and parameter explanations in logical order. Every sentence adds value with zero wasted text, making it easy to parse.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which covers return values), the description provides excellent context: clear purpose, sibling differentiation, detailed parameter semantics, and behavioral transparency about what the tool returns. This is complete for a search tool with output schema support.

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

Parameters5/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 compensate fully. It provides detailed semantic explanations for all 4 parameters: query purpose, limit range and default, category options with explicit enum values, and days_back meaning. This adds substantial value beyond the bare 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 searches for 'balanced news stories — AI-synthesized articles that aggregate multiple sources' and explicitly distinguishes it from sibling tool 'search_news' which returns individual RSS articles. This provides specific verb+resource differentiation.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: 'Unlike search_news (which returns individual RSS articles), this returns Helium's own synthesized stories.' This directly addresses sibling tool differentiation with clear context.

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/connerlambden/helium-mcp'

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