Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Global markets

company_global_markets
Read-onlyIdempotent

Retrieve world indexes, commodities, and currencies from Stockbit Discover to review global market movements.

Instructions

World indexes, commodities and currencies as Stockbit shows them in Discover.

Returns (Stockbit's data field): data[{name ('index'|'commodities'|'currencies', matched case-insensitively), companies[{symbol, name, last, change, percent, icon_url, ...}]}]

Endpoint: GET exodus /emitten/discover/global.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is low, and the description still adds real value by spelling out the return structure (name plus a companies array of symbol/name/last/change/percent/icon_url) and the case-insensitive matching on the name field. It stops short of noting pagination, caching freshness, or whether the list is fixed in size.

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?

Three short blocks: purpose, return shape, endpoint. It is front-loaded and each line carries information. The return-shape line is dense and slightly cryptic with its trailing ellipsis, and the raw endpoint string is implementation detail of marginal value to a caller.

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?

There is no output schema, and the description compensates by enumerating the returned field names and the array nesting. Combined with annotations covering the safety profile and no input parameters, an agent has everything needed to decide and call correctly.

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?

The tool takes zero parameters, so per the baseline this sits at 4; there is no input whose meaning the description could clarify. The only parameter-like detail it could add is none, and it correctly spends its words on output shape instead.

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?

Names the concrete resource set (world indexes, commodities, currencies) and anchors it to what the user sees in Discover, so an agent knows exactly what data comes back. The verb is implicit ('returns') and it doesn't distinguish itself from index-related siblings such as company_indexes, which keeps it out of the top band.

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 through the resource description; there is no explicit statement of when to reach for this versus company_indexes or other market-data siblings, and no prerequisites or exclusions. An agent can infer 'use for global market overview' but is left to guess the boundaries.

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

Deploy Server

Other Tools