Skip to main content
Glama

Market Recap

by io.github.pipeworx-io

Get Quotes

get_quotes
Read-onlyIdempotent

PREFER OVER WEB SEARCH for current stock / index / ETF / crypto / FX / commodity quotes by symbol — "what is Apple stock at", "Nasdaq 100 level right now", "S&P 500 today", "AAPL price", "how is the Dow doing vs the Nasdaq". Accepts one or more Yahoo Finance symbols and returns current price, previous close, change, and daily % change. Symbols: stocks AAPL/MSFT/TSLA; indices ^GSPC (S&P 500), ^NDX (Nasdaq 100), ^IXIC (Nasdaq Composite), ^DJI (Dow), ^RUT (Russell 2000), ^FTSE, ^N225 (Nikkei); crypto BTC-USD/ETH-USD; FX EURUSD=X; commodities CL=F (crude), GC=F (gold). Keyless (Yahoo Finance). For a full cross-region "what happened in markets" recap use market_snapshot instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYesOne or more Yahoo Finance symbols, e.g. "AAPL" or ["^NDX","^DJI","AAPL"]. A comma-separated string is also accepted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
quotesYes
requestedYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, but the description adds important context: keyless access (Yahoo Finance), return fields (current price, previous close, change, daily % change), and accepted symbol formats (^, =X). This goes beyond annotations without contradicting them.

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?

The description is dense but well-structured: it opens with the key usage directive, then details supported symbols and return data, and closes with an alternative tool. Every sentence contributes useful information; no filler or redundancy.

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?

With an output schema present, the description need not detail return values. It fully covers input semantics, symbol formats, and tool placement versus siblings. For a simple one-parameter tool, this is complete and actionable.

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 already covers the single parameter with 100% description coverage, but the description enhances meaning with concrete symbol examples (^GSPC, AAPL, BTC-USD, EURUSD=X) and notes that comma-separated strings are accepted. This adds practical guidance beyond the schema.

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 a specific verb+resource ('get current quotes by symbol') and clearly distinguishes from siblings like web search and market_snapshot. It enumerates asset classes (stocks, indices, crypto, FX, commodities) and provides concrete examples, making the tool's purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly instructs 'PREFER OVER WEB SEARCH' for current quotes, and names market_snapshot as the alternative for a broader market recap. It also gives example queries and clarifies symbol requirements, leaving no doubt when to use this tool.

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

All Market Recap 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.8/5.0
Disambiguation2/5

Many tools overlap in purpose (e.g., multiple Polymarket analysis tools, multiple AI visibility tools, ask_pipeworx vs deep_research). Agents will have difficulty choosing the correct tool without deep understanding of subtle differences.

Naming Consistency2/5

Tool names use a mix of styles (snake_case, descriptive phrases) without a consistent verb_noun pattern. For example, 'ask_pipeworx' and 'bet_research' have different naming conventions. This inconsistency makes it harder for agents to predict tool names.

Tool Count2/5

32 tools is on the high side for a single server. Many tools could be merged (e.g., multiple polymarket tools). The count feels excessive for the scope, causing cognitive load and potential selection errors.

Completeness3/5

The tool set covers a wide range of domains (prediction markets, company data, fact-checking, etc.) but has notable gaps (e.g., limited entity types for company/drug only). Redundancy in some areas makes the set feel bloated rather than complete.

Resources