Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

stock

Live equity quote for a ticker: last price, open/high/low/close, volume and previous close.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. AAPL, MSFT, ^GSPC, VOD.uk

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does useful work by declaring the response fields in the absence of an output schema, but it omits whether quotes are real-time or delayed, behavior outside market hours, invalid-symbol errors, and any rate limits — meaningful gaps for a live market-data call.

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

Conciseness5/5

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

A single front-loaded sentence naming the resource and its return fields with zero filler. Nothing pads it and nothing essential is buried.

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?

For a one-parameter tool with no output schema, enumerating the returned fields is exactly the compensation needed. The remaining omission — data freshness/delay and failure behavior — is a modest gap rather than a blocker for correct invocation.

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?

Only one parameter and schema coverage is 100%; the schema already documents 'symbol' with examples including index (^GSPC) and non-US (VOD.uk) formats. The description only echoes 'ticker' and adds no format or interpretation detail beyond the schema.

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+resource ('Live equity quote for a ticker') and enumerates the payload (last price, OHLC, volume, previous close). 'Equity'/'ticker' distinguishes it from the crypto and FX siblings, though the description never names those alternatives 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?

Use is only implied by the word 'Live' — an agent can infer this is for current quotes rather than history or conversion. There is no explicit when-to-use, when-not-to-use, or pointer to crypto/fx/get_crypto_prices for non-equity instruments.

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

All GadgetHumans API Hub 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