Skip to main content
Glama
shigechika

jquants-mcp

by shigechika

compare_close_vs_vwap

Read-onlyIdempotent

Identify buying or selling pressure by comparing a stock's closing price to its daily VWAP.

Instructions

Compare a stock's close to its daily VWAP (買い圧力・売り圧力) for one code. All plans.

Use for VWAP・買い圧力・売り圧力 queries on a specific stock; not a cross-sectional screener. Close above VWAP = buying pressure; below = selling pressure. VWAP = Va/Vo (None when Vo=0). Data available ~17:15 JST on trading days.

[Supported plans] Free / Light / Standard / Premium (cache-only, no API call)

Args: code: Stock code (required). date: Single trading date (YYYYMMDD or YYYY-MM-DD). Overrides date_from/date_to. date_from: Range start inclusive (YYYYMMDD or YYYY-MM-DD). date_to: Range end inclusive (YYYYMMDD or YYYY-MM-DD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
dateNo
date_fromNo
date_toNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Adds context beyond annotations: explains what VWAP measures, data availability (~17:15 JST), plan restrictions, and the cache-only nature. No contradiction with annotations.

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 core purpose, followed by structured Args. Slight redundancy but overall clear and efficient.

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?

Covers interpretation, data timing, plan support, and parameter details. With an output schema present, the lack of return value explanation is acceptable.

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?

Despite 0% schema coverage, the description includes an Args section explaining each parameter, including format hints (YYYYMMDD or YYYY-MM-DD) and the override behavior of date over date_from/date_to.

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 states it compares a stock's close to its daily VWAP for one code, using a specific verb and resource. It also clarifies it is not a cross-sectional screener, distinguishing it from sibling tools.

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?

Explicitly states use for VWAP/buying pressure queries on a specific stock and mentions it is not a cross-sectional screener. Could name specific alternative tools but still provides clear guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shigechika/jquants-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server