Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Stock Exchange

StockExchange
Read-only

Stock Exchange: Stock Exchange identifies trading venues worldwide by Market Identifier Code, name, or country. It provides official exchange names, acronyms, host cities, websites, and founding dates, while paid plans add regulatory MIC and LEI identifiers. (Cost: 2 credits)

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

Input Schema

NameRequiredDescriptionDefault
micNoThe 4-character Market Identifier Code (e.g., XNYS for NYSE, XNAS for NASDAQ)
nameNoSearch exchanges by name (partial match supported)
countNoMaximum number of results to return (default: 2)
countryNoISO 2-letter country code (e.g., US, GB, JP)

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: the full set of returned attributes, the fact that regulatory MIC and LEI fields are gated behind paid plans, and a stated cost of 2 credits — all relevant to an agent deciding whether to call it.

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?

Two sentences, front-loaded with the core purpose and followed by return-value and cost context; nothing is filler. The only slack is the redundant 'Stock Exchange: Stock Exchange identifies' opening, which repeats the title verbatim.

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?

An output schema exists, so return-shape explanation is optional, yet the description still summarizes what comes back and flags plan-dependent fields. Combined with a fully documented 4-parameter schema and clear read-only annotations, an agent has everything needed to call it correctly.

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% with per-parameter descriptions and examples, so the schema carries the parameter burden. The description reinforces that mic, name and country are the lookup axes but adds no syntax, matching behavior, or default/pagination detail beyond what the schema already states.

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?

The description uses a specific verb and resource: 'identifies trading venues worldwide by Market Identifier Code, name, or country', and enumerates the attributes returned. It is unambiguous about what it does, though it never names a sibling (e.g. GlobalStockMarket, TickerSymbols, StockMarketOpenTimes) to sharpen the boundary.

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?

Usage is only implied: the three lookup keys tell an agent roughly how it can be queried, but there is no explicit when-to-use or when-not-to-use guidance. With reference-data siblings like GlobalStockMarket and TickerSymbols present, the description leaves the agent to infer that this tool is for exchange metadata rather than prices or listings.

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