Skip to main content
Glama
Sign In

PickSkill

by ai.pickskill
OverviewDiscussionsAdmin

Stock technical signals

get_stock_signals

Technical signals for up to 10 US, Hong Kong or China A-share stocks: latest close, 1-day and 5-day change, and 8 indicator dimensions (MACD, MA, RSI, KDJ, Bollinger, ADX, volume, money flow), each bullish / bearish / neutral with a 5-day trail and the latest values (e.g. RSI, KDJ K/D/J, MACD DIF/DEA). Counts as one conversation against your PickSkill plan.

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": {
      "tickers": "<tickers>"
    },
    "name": "get_stock_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesYahoo Finance ticker: US 'NVDA', 'BRK-B'; Hong Kong '0700.HK'; Shanghai '600519.SS'; Shenzhen '300750.SZ'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and adds meaningful behavior: it discloses the 10-ticker cap, the output structure including a 5-day trail, and a billing cost of one conversation against the PickSkill plan. It does not mention data freshness, market-hours behavior, or error handling for invalid tickers.

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 front-loaded with the core purpose and then efficiently enumerates the indicators and output values. The billing sentence is short and relevant, and no sentence is wasted.

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 read-style signal retrieval tool with no output schema, the description adequately explains what is returned, including indicator dimensions and latest values. It is slightly incomplete on operational behavior such as data latency and failure modes, but the core calling context is covered.

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 coverage is 100%, and the schema already documents the ticker format for US, Hong Kong, Shanghai, and Shenzhen listings, plus the 1–10 item range. The description reinforces the supported markets and cap but adds no syntax or format details beyond the schema.

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 (technical signals), supported markets, and exact output dimensions, so the tool's function is clear. It does not explicitly contrast with siblings such as get_earnings_highlights or get_my_portfolio, so sibling differentiation is only implicit.

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?

Usage is implied by the content: an agent can infer this is for technical indicator snapshots on up to 10 tickers. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for portfolio-level or earnings queries.

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

All PickSkill 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