Skip to main content
Glama

veroq_ticker_price

Get live market prices for stocks and cryptocurrencies. Check current price, change percentage, volume, and market status for any ticker symbol.

Instructions

Get the live market price for a stock or crypto ticker.

WHEN TO USE: For a quick price check on any ticker. This is free — use it freely. For full analysis, use veroq_full instead. RETURNS: Current price, change, change percent, volume, currency, and market state (open/closed). COST: Free (0 credits). EXAMPLE: { "symbol": "AAPL" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTicker symbol (e.g. AAPL, NVDA, BTC)
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses COST ('Free (0 credits)') and provides a RETURNS section detailing the output fields (price, change, volume, market state). Could be improved by mentioning rate limits or data freshness, but covers the essential behavioral traits well.

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?

Uses clear section headers (WHEN TO USE, RETURNS, COST, EXAMPLE) making it highly scannable. Every line provides distinct information. Front-loaded with core purpose. No filler text—excellent information density.

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?

For a simple single-parameter tool without output schema, the description is comprehensive. It compensates for missing output schema by documenting return fields. Includes cost information critical for API tools. No gaps given the tool's complexity.

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?

Schema has 100% coverage with parameter descriptions, setting baseline at 3. The description adds value by providing a complete JSON 'EXAMPLE' showing exact invocation format, and reinforces valid inputs by mentioning both 'stock or crypto ticker' in the main description.

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?

The description states exactly what the tool does: 'Get the live market price for a stock or crypto ticker' using a specific verb and resource. It clearly distinguishes from sibling tool veroq_full by contrasting 'quick price check' with 'full analysis'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains an explicit 'WHEN TO USE' section stating 'For a quick price check on any ticker.' Explicitly names the alternative: 'For full analysis, use veroq_full instead.' Also includes cost guidance ('This is free — use it freely'), which informs usage decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Veroq-ai/veroq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server