Skip to main content
Glama

AgentHC Market Intelligence

get_news_sentiment

Market news sentiment analysis with breaking news detection.

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_news_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoResponse format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.full
include_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "full",
      +  "description": "Response format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.",
      +  "enum": [
      +    "full",
      +    "compact",
      +    "prompt",
      +    "agent"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description must disclose behavior; it only states that sentiment analysis and breaking-news detection occur. It omits data sources, freshness or latency, coverage, authentication, rate limits, and whether the tool is read-only, leaving the agent with little operational context.

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 a single front-loaded sentence with no filler. It is arguably too terse for a tool with multiple response modes, but every word contributes to the stated purpose.

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

Completeness2/5

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

With no annotations and no output schema, the description should carry more of the operational burden. It omits return format, breaking-news detection semantics, and include_prompt behavior, so an agent lacks enough detail to invoke it confidently.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description mentions neither parameter. The format enum is documented in the schema, but include_prompt has no description anywhere, so the description fails to compensate for the coverage gap.

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?

The phrase 'Market news sentiment analysis' names a specific resource and operation, and 'breaking news detection' adds a distinct capability, so an agent can identify it as a sentiment/news tool. It does not explicitly contrast with sibling data tools, though their domains differ enough that confusion is limited.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no alternative named. 'Breaking news detection' hints at urgency but does not say when this tool is preferable to a market snapshot or economic calendar.

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