Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Ticker Symbols

TickerSymbols
Read-only

Ticker Symbols: Ticker Symbols identifies what a ticker symbol is and where it trades. Look up a symbol to get every listing that carries it across the US and 18 international stock markets, cryptocurrencies, futures and currency pairs, or find a stock symbol by company name. Every result carries its name, market, exchange, security type and asset class; paid plans add FIGI identifiers, SEC CIK numbers and fuller search results. (Cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
marketNoKeep only listings on this market: a two-letter market code, CRYPTO, FUTURES or FX for currency pairs.
searchNoSearch listings whose name words or symbol start with this text, for example toyota or berkshire hath. Returns up to 10 listings (3 on the free plan).
symbolNoThe ticker symbol to look up, for example AAPL, BRK.B, SHEL or 7203. Returns every listing with that symbol. A suffix such as BP.L, a coin pair such as BTC-USD or a contract such as CL=F narrows it to that market.
assetClassNoKeep only listings of this asset class.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, and the description adds context they don't carry: a 1-credit cost, that paid plans unlock FIGI identifiers, SEC CIK numbers and fuller search results. It does not mention rate limits or whether symbol-only matching is exact, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and dense, but it opens with a circular restatement ('Ticker Symbols identifies what a ticker symbol is') that consumes space without adding information. The remaining content is efficient and pays for itself.

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?

An output schema exists, and the description nevertheless summarizes returned fields (name, market, exchange, security type, asset class), which is more than adequate for a zero-required-parameter lookup tool. Nothing essential to correct invocation is missing.

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%, so the parameters are already documented including examples for market, search, symbol and assetClass. The description adds only a light gloss — that a company name can be supplied to find a symbol — so baseline 3 applies.

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?

States a specific verb and resource: look up a ticker symbol to get every listing that carries it, or reverse-search a symbol from a company name, across US and 18 international markets plus crypto, futures and FX. Clear and distinguishable from TickerNews or CompanyLookup by the symbol-listing framing, though no sibling is named explicitly.

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?

Two usage modes are described (by symbol, or by company name), which implies when to call it. However, there is no explicit guidance on when to prefer it over nearby tools like CompanyLookup, StockExchange or GlobalStockMarket, and no stated prerequisites.

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

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