Skip to main content
Glama
Sign In

Wealthnow

by io.wealthnow
OverviewDiscussionsAdmin

News Brief

news_summary
Read-onlyIdempotent

One-shot news intelligence for a ticker: stories of the last 24 hours (news_count_24h counts them all; the newest 20 are listed), 7-day sentiment stats, trending stories of the last 72 hours, structured events, and analyst actions in a single parallel fetch (90s TTL). THE primary tool for 'what's the news on X?': this ALONE answers most single-ticker news questions; do NOT stack other news tools in the same round unless it returns nothing useful. analyst_actions carries only part of the street's rating actions (analyst_actions_note): an empty list is none in the feed, not none taken.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "news_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker symbol, for example AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, openWorld, idempotent, non-destructive), so the bar is lower, yet the description adds substantial operational context beyond them: a 90s TTL, the 24h listing cap (counts all but lists newest 20), and the critical caveat that an empty analyst_actions list means 'none in the feed, not none taken.' That final nuance actively prevents a downstream misinterpretation.

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?

Dense and front-loaded: the payload is described first, then the routing rule, then the analyst_actions caveat. Every sentence carries information, though the parenthetical stacking (news_count_24h, 90s TTL, analyst_actions_note) makes it slightly heavy to parse in one pass.

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?

No output schema exists, so the description must carry the return-shape burden, and it does: it names each returned component (24h stories, sentiment stats, trending, events, analyst actions) and discloses the listing cap and empty-list semantics. Nothing needed to call or interpret the result is missing.

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?

With a single parameter at 100% schema description coverage, the schema fully documents 'ticker' with an example. The description adds nothing about the parameter's format or constraints beyond what the schema already states, so the baseline 3 applies.

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?

States a specific verb+resource ('one-shot news intelligence for a ticker') and enumerates the concrete payload: 24h stories, 7-day sentiment stats, 72h trending stories, structured events, and analyst actions. It explicitly positions itself against sibling news tools ('do NOT stack other news tools'), so an agent can distinguish it without opening another schema.

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?

Gives explicit when-to-use ('THE primary tool for what's the news on X?') and when-not-to-use ('this ALONE answers most single-ticker news questions; do NOT stack other news tools in the same round unless it returns nothing useful'). This is a direct routing rule naming the alternative behavior, not an inference.

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

All Wealthnow 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