Skip to main content
Glama
Sign In

highbrow_fame data APIs (pay per call)

by io.github.projectworks007
OverviewDiscussionsAdmin

Quotes for stocks, ETFs, indices, currencies and crypto pairs

finance_quotes
Read-only

Quotes for up to 25 symbols in one call: stocks, ETFs, indices, currencies and crypto pairs (for example AAPL, VOD.L, ^GSPC, EURUSD=X, BTC-USD). Returns price, change, day range, volume, 52-week range, market cap and valuation ratios; optional price history and fundamentals. Suited to market-data lookups. $0.005 per call.

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

Input Schema

NameRequiredDescriptionDefault
historyNoPrice history range.
symbolsNoComma-separated symbols, e.g. AAPL,MSFT,VOD.L,SAP.DE,BTC-USD,EURUSD=X,^GSPC.
intervalNoHistory interval (intraday intervals only for short ranges).
fundamentalsNoInclude company data (sector, revenue, margins, cash, debt, analyst targets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts: the 25-symbol cap, the exact returned fields (price, day range, 52-week range, market cap, valuation ratios), and a per-call cost of $0.005. Cost and batching limits are exactly the kind of context an agent cannot get from structured fields, though truncation/error behavior for invalid tickers is unstated.

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 the core capability and batching limit, then the instrument examples, then return fields, then cost — a sensible ordering. The return-field enumeration is long but each clause carries information; only the trailing 'Suited to market-data lookups' is filler.

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?

No output schema exists, and the description compensates by listing return fields and the optional history/fundamentals payloads, plus the call cap and price. For a read-only lookup tool this is nearly complete; what remains missing is failure behavior for unknown symbols and any pagination or rate-limit detail.

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 description coverage is 100%, so all four parameters (symbols, history, interval, fundamentals) are already documented, establishing a baseline of 3. The description adds marginal meaning by noting price history and fundamentals are optional and by restating symbol-format examples, but adds no syntax, ranges, or allowed values 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?

States a specific verb+resource ('Quotes for up to 25 symbols in one call') and enumerates the covered asset classes with concrete example tickers (AAPL, VOD.L, ^GSPC, EURUSD=X, BTC-USD). An agent knows exactly what this returns and for which instrument types, and none of the sibling tools overlap with market data.

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 only usage guidance is the one-liner 'Suited to market-data lookups', which is implied usage rather than a rule. There are no exclusions, no prerequisites, and no routing advice (e.g. when to request history/fundamentals vs. a plain quote). Adequate but thin.

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

All highbrow_fame data APIs (pay per call) 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