Quantral Stock Sentiment

Strategy

get_strategy

Read-onlyIdempotent

Returns one Quantral strategy in detail: the plain summary and caveats, what it is based on, the current list of stocks (which are new this update and each one's move since it joined), the names dropped in the latest update, the next update date, and key stats. Strategies are tracked model portfolios built by fixed rules, not recommendations or investment advice; live and backtest records are reported separately. Returns are before trading costs.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Strategy slug, e.g. insider-buying, finx-stars, capitol, deep-dives, lone-bulls.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

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."

Changed1 schema field changedOct 4, 2026

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."

AddedSep 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior, so the description adds useful domain transparency instead of repeating safety hints. It discloses the returned components, caveats, live-versus-backtest separation, exclusion of trading costs, and the fact that strategies are not investment advice.

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 definition is front-loaded with the core purpose and then enumerates the returned contents without filler. The first sentence is dense and long, but every clause carries meaningful scope information.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so comprehensively: summary, caveats, basis, current stocks, dropped names, next update date, key stats, and live/backtest separation. For a single-parameter read tool, the description is complete enough for correct invocation.

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?

Schema description coverage is 100%, and the slug parameter is already documented with examples in the schema. The description does not add syntax, format, or lookup guidance for the slug beyond what the schema provides, so it meets the baseline for a fully described single parameter.

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 description states a specific verb and resource: it returns one Quantral strategy in detail, with a clear list of what that detail includes. It implicitly distinguishes itself from list_strategies by specifying one strategy, but it does not explicitly name any sibling tool as the alternative.

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?

The description explains domain context, such as strategies being tracked model portfolios and live/backtest records being separate, but it gives no explicit when-to-use guidance. It does not tell the agent to use list_strategies to discover a slug or get_strategy_changes for a change-focused view.

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 tools Inspect

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

Need Help?