Skip to main content
Glama
Sign In
Open Stocks MCP

Open Stocks MCP

by Open-Agent-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

top_movers_sp500

Identify the top gaining or declining S&P 500 stocks each day. Specify direction to see either the biggest gainers or losers.

Instructions

Gets top S&P 500 movers for the day.

Args:
    direction: Direction of movement, either 'up' or 'down' (default: 'up')

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

Input Schema

NameRequiredDescriptionDefault
directionNoup

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided. The description implies a read-only operation but does not explicitly disclose safety, auth needs, or rate limits. For a simple read tool, this is adequate but minimal.

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 two sentences, front-loaded with the purpose, and includes only necessary information about the parameter. No wasted words.

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?

Given the tool has only one parameter (with default), no required parameters, and an output schema exists, the description adequately covers the tool's purpose and parameter. It is complete for a simple read tool.

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?

The only parameter 'direction' has 0% schema description coverage, but the description adds meaning: 'Direction of movement, either 'up' or 'down' (default: 'up')'. This clearly explains the parameter's purpose and default value.

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 clearly states the verb 'Gets', the resource 'top S&P 500 movers', and the scope 'for the day'. This distinguishes it from siblings like 'top_movers' and 'top_100_stocks'.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives like 'top_movers' or 'top_100_stocks'. Usage is implied but lacks explicit guidance on context or exclusions.

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

Deploy Server

Other Tools