Skip to main content
Glama

Gloria AI

by io.github.cryptobriefing-labs

get_enriched_news

Get enriched news with full AI-generated context and analysis (paid via x402).

This premium endpoint returns the complete news data including:
- long_context: Detailed AI-generated context about the news event
- short_context: Brief contextual summary
- Full entity analysis and token mentions

Payment is handled via the x402 protocol using USDC on Base network.
This tool returns the payment endpoint and instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A3.9/5.0
Behavior4/5

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

Given no annotations, the description fully carries the burden of behavioral disclosure. It clearly indicates that this is a paid endpoint, describes the return data structure (long/short context, entity analysis), and explains payment handling via USDC on Base network. No behavioral traits are hidden.

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 concise with clear sections explaining the premium nature, return fields, and payment mechanism. It avoids fluff but could be slightly more streamlined by removing redundant phrasing like 'full entity analysis and token mentions' which is already implied by 'complete news data'.

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 zero-parameter tool with no output schema and no annotations, the description adequately explains the tool's premium nature, return structure, and payment details. It is complete enough for an agent to understand when to invoke it, though it could mention any rate limits or authentication requirements.

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 has no parameters and is 100% covered (no params to cover). The description adds value by explaining what the tool returns, but there are no parameters to elaborate on. Baseline 3 is appropriate as the description does not need to add parameter 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 that the tool retrieves enriched news with AI-generated context and analysis, differentiating it from siblings like 'get_latest_news' and 'get_news_item' by highlighting the premium AI context and payment requirement.

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 explains when to use this tool (for enriched AI context) but does not explicitly state when not to use it or name alternatives. It mentions payment via x402 but lacks guidance on prerequisites or comparison with sibling tools.

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

All Gloria AI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_enriched_news lacks clear parameters, making it ambiguous whether it returns a specific item, the latest, or category-based news. This could cause confusion with get_latest_news or get_news_item.

Naming Consistency5/5

All tool names follow a consistent 'get_<noun>' pattern, making the naming predictable and easy to interpret.

Tool Count5/5

Seven tools is well-scoped for a crypto news API, covering essential operations without being too few or too many.

Completeness5/5

The tool set covers the core workflow: listing categories, fetching latest news, searching, getting details, recaps, and premium enrichments. No obvious gaps for a read-only news service.

Resources