Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

Stock Price

agentbit.stock_price
Read-onlyIdempotent

Latest equity quote from a free, key-less source (Yahoo Finance): price, day open/high/low, previous close, % change, volume and currency. Input a symbol like AAPL. Delayed, $0.005. Pay-per-call via x402 (USDC, Base).

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": "agentbit.stock_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesEquity ticker, e.g. AAPL
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the data source, delayed data, the $0.005 per-call cost, and the x402 USDC/Base payment mechanism. It also lists the exact quote fields returned, giving the agent an accurate behavioral model without an output schema.

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?

Three short sentences lead with the core purpose and return fields, then the input example, then cost and latency caveats. Every sentence carries information without repeating schema details.

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 tool with one required parameter, full schema coverage, and safety annotations, the description provides everything needed to invoke it correctly: what data is returned, how to pass the symbol, and what it costs. The listed fields compensate for the absent output schema.

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%, so the schema already documents symbol and _payment. The description adds a concrete symbol example and payment context but does not materially extend parameter semantics beyond the schema.

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 opens with 'Latest equity quote' and names Yahoo Finance as the source, enumerating the specific fields returned. The qualifier 'equity' clearly differentiates this from sibling quote tools like agentbit.token_price and agentbit.fx.

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

Usage Guidelines4/5

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

The description gives clear usage context: input an equity symbol like AAPL. It does not explicitly name alternatives or state when not to use it, but the 'equity' scope is enough to rule out crypto and currency siblings.

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

All AgentBIT 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