Skip to main content
Glama

welcome

by com.thebalancedinvestorclub

get_close_history

Read-onlyIdempotent

Daily close-price history for a stock, ETF, or crypto pair over a selected range. Summary stats by default (start, end, high close, low close, percent change). Optionally returns the most recent N daily closes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoTime range. Defaults to 1Y.
tickerYesTicker (e.g. AAPL, SPY) or crypto pair (e.g. BTC-USD, ETH-USD).
intervalNoSampling interval for the returned closes (last close of each week/month). Defaults to daily. Combine with range='ALL' and include_recent=60 for up to 5 years of monthly closes.
asset_typeNoAsset type. Defaults to 'stock'. Use 'crypto' for pairs like BTC-USD.
include_recentNoOptional: also return the most recent N closes at the chosen interval (max 60).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds concrete behavioral details: output defaults to summary statistics (start, end, high/low close, percent change) and optionally recent closes. This goes beyond the schema and annotations.

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?

Two sentences, front-loaded with the core function. Every word earns its place, and the structure is clear and scannable.

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?

The description adequately covers the main return behavior and options, especially since there is no output schema. It could mention interval options, but the schema covers those details, making the description complete enough for a read-only tool.

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% with thorough parameter descriptions. The tool description adds no unique parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 tool retrieves daily close-price history for stocks, ETFs, or crypto pairs over a selected range. It also specifies default summary stats and optional recent closes, distinguishing it from siblings like get_price_alignment.

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?

The description clearly implies use when historical close prices are needed for a ticker over a range. It does not explicitly name alternatives or state when-not-to-use, but the context is unambiguous.

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

All welcome toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

With 57 tools, most have distinct purposes (market data, journaling, watchlists). A few related tools (get_price_alignment vs get_crypto_price_alignment, get_market_pulse vs get_market_movers) could cause miselection, but descriptions clarify asset types and scope.

Naming Consistency4/5

Tools predominantly use get_/list_/create_/update_/delete_ verbs with clear noun suffixes. Minor deviations like start_here, whoami, add_to_watchlist, and remove_from_watchlist break the pure verb_noun pattern, but the style is consistent and readable.

Tool Count1/5

At 57 tools, the server is far beyond the well-scoped range. While the domain is broad, this many tools will overwhelm an agent's capability to select accurately, and many could be consolidated (e.g., separate financial statements).

Completeness5/5

The server covers watchlist CRUD, trading journaling, market data (fundamentals, statements, news, transcripts), analysis tools, and community features. No obvious dead ends; lifecycle coverage is thorough for the described domain.

Resources