Skip to main content
Glama
Sign In

Quantral Stock Sentiment

by com.quantral
OverviewDiscussionsAdmin

Upcoming events

get_upcoming_events
Read-onlyIdempotent

Returns upcoming corporate events: earnings (before open or after close), ex-dividend dates, splits and investor days, soonest first. With a ticker, one company's events; without one, a list across the companies in the scope: top (the names with the strongest chatter now), watchlist (the signed-in account's watchlist) or all. Dates are US market dates.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look (1-60, default 14).
limitNoNumber of events to return (1-50, default 20).
scopeNoWhich companies when no ticker is given.top
tickerNoTicker symbol for one company's events, for example NVDA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, idempotent operation. The description adds useful behavioral context beyond the annotations: event types, chronological ordering, scope-dependent company selection, and the fact that dates are US market dates. It does not discuss pagination or rate limits, but those are not central for this read-only lookup.

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 tightly written and front-loaded with the tool's purpose, then the ticker-vs-scope behavior and date convention. Every sentence carries useful information, with no redundant restatement of the name or schema.

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?

For a read-only lookup tool with no output schema, the description covers what is returned, the event categories, ordering, ticker behavior, scope behavior, and date basis. Combined with the fully described input schema and annotations, an agent has enough information to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents days, limit, scope, and ticker. The description still adds meaning by defining how ticker changes behavior and by explaining what the scope enum values mean in practice: top is strongest chatter, watchlist is the signed-in account's watchlist, and all is all companies in scope.

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 states a specific verb and resource: it returns upcoming corporate events. It enumerates the event types (earnings, ex-dividend dates, splits, investor days) and the ordering (soonest first), so an agent can tell what this tool does without opening the schema.

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

Usage Guidelines4/5

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

It clearly explains the two usage modes: with a ticker, one company's events; without one, events across a selected scope. It also defines the scope choices, though it does not explicitly name when to use another tool instead or any exclusions.

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

All Quantral Stock Sentiment 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