Skip to main content
Glama
jmthomasofficial

JMT x402 MCP Server

stock_quote

Retrieve live stock quotes for any ticker symbol. Each call costs $0.03, paid via USDC on Base mainnet using x402.

Instructions

Live stock quote. Price: $0.03/call via x402 (USDC on Base mainnet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoTicker (default: AAPL)
Behavior2/5

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

With no annotations, the description carries full disclosure burden. It mentions a cost per call, which is unusual, but fails to disclose authorization needs, rate limits, or side effects. The pricing info is behavioral but incomplete.

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?

The description is short (one sentence) with no wasted words. However, it could be restructured to include standard info like return value before pricing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should explain the return format. It fails to mention what data the quote includes (e.g., price, volume, timestamp). The pricing detail is not standard for completeness.

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 description adds no extra value beyond the schema's parameter description ('Ticker (default: AAPL)'). Baseline score of 3 is appropriate since the schema already documents the parameter.

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 states 'Live stock quote', which clearly indicates the tool returns a stock price. It distinguishes from sibling tools like 'crypto_price' for crypto assets. However, it doesn't specify what the quote includes (e.g., price, change) or that it's a read operation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description mentions pricing but does not specify when to prefer this over tools like 'market_pulse' or 'news_briefing' for broader market data.

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/jmthomasofficial/x402-mcp-server'

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