Skip to main content
Glama
Sign In

Quantral Stock Sentiment

by com.quantral
OverviewDiscussionsAdmin

Strategy changes

get_strategy_changes
Read-onlyIdempotent

Returns which stocks were added to and dropped from a Quantral strategy's list. Without since, it covers the latest update (added and dropped versus the list before). With since (YYYY-MM-DD), it returns the net difference between the list as of that date and the current list, so a name that was added and dropped again in between does not appear. Added names carry their move since they joined; dropped names carry how they did while in the list (pending until their last week is scored). Strategies are tracked model portfolios built by fixed rules, not recommendations; these are changes to the list, not trades.

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": {
      "slug": "<slug>"
    },
    "name": "get_strategy_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesStrategy slug, e.g. insider-buying, finx-stars, capitol, deep-dives, lone-bulls.
sinceNoStart date for the comparison, as YYYY-MM-DD. When absent, only the latest update is compared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Strategy slug, e.g. insider-buying, finx-stars, capitol, deep-dives."New value: +"Strategy slug, e.g. insider-buying, finx-stars, capitol, deep-dives, lone-bulls."
  2. Changed2 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"The date the user last looked, as YYYY-MM-DD. Omit for the latest update only."New value: +"Start date for the comparison, as YYYY-MM-DD. When absent, only the latest update is compared."
    • changedInput schema / properties / slug / description
      Previous value: -"Strategy slug from list_strategies, e.g. insider-buying, finx-stars, capitol, deep-dives."New value: +"Strategy slug, e.g. insider-buying, finx-stars, capitol, deep-dives."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world behaviour, and the description still adds substantive semantics beyond them: the since mode is a net diff so add-then-drop names are excluded, and dropped names' returns stay pending until their last week is scored. It also pre-empts misinterpretation by noting these are model-portfolio list changes, not trades.

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?

Front-loaded with the core effect, then the two modes, then return semantics, then a framing caveat. It is dense but every clause carries information; the final sentence about strategies not being recommendations could be trimmed for a strict reading.

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?

With no output schema, the description supplies the return-value semantics itself: added names carry performance since joining, dropped names carry performance while held and may be pending. Combined with the mode definitions, an agent has everything needed to call and interpret it.

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 coverage is already 100%, yet the description goes further by explaining the computational semantics of since (difference against the list as of that date, not an event log) and the exact default when it is omitted, which the schema only gestures at.

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 and resource ('Returns which stocks were added to and dropped from a Quantral strategy's list') and defines what a strategy is, which cleanly separates it from the sibling get_strategy that returns the list itself rather than its changes.

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?

The two modes are spelled out with their selection condition: omit since for the latest update, supply since for a net difference from that date. It doesn't explicitly name get_strategy as the alternative for full-list reads, so routing is implied rather than stated.

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