Skip to main content
Glama

OptionWhales

Options flow momentum rankings

momentum_rankings
Read-onlyIdempotent

Tickers ranked by options-flow momentum (the fastest-changing positioning this session). Use for 'which stocks have the strongest options momentum right now?'. Free accounts: top 3; Pro: up to 200 with all fields.

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

Input Schema

NameRequiredDescriptionDefault
topNoTickers to return (default 50)

Output Schema

NameRequiredDescriptionDefault
metaNo
previewNo
sessionNo
rankingsYes
total_tickersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "meta": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "preview": {
      +      "type": "string"
      +    },
      +    "rankings": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "coherence_last": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "direction_bias": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "intent_label": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "intent_primary": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "momentum_fast": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "momentum_slow": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "strength_last": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "ticker": {
      +            "type": "string"
      +          },
      +          "volume_total": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "ticker"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "session": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total_tickers": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "rankings"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. The description adds useful behavioral context beyond annotations: ranking is session-based and account tier limits the result size to top 3 for free accounts or up to 200 for Pro.

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 short, front-loaded with the ranking definition, followed immediately by the intended query and account limits. Every sentence adds distinct value with no wasted wording.

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

Completeness4/5

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

For a one-parameter ranking tool with an output schema, the description covers purpose, usage, ranking basis, and account-tier constraints. It is complete enough to call correctly, though it could clarify what qualifies as 'momentum' in more concrete terms.

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 top parameter is already documented with its default and maximum. The description adds plan-specific meaning by clarifying that free accounts return only the top 3 while Pro accounts can request up to 200 with all fields.

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 resource and ranking basis: tickers ranked by options-flow momentum, defined as fastest-changing positioning this session. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling tools such as directional_current or abnormal_trades_current.

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 gives a clear usage context with the example query 'which stocks have the strongest options momentum right now?'. It does not state when not to use it or name alternative tools, so it stops short of full routing guidance.

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