Skip to main content
Glama

Stock premiums on Robinhood Chain

brainchain_stock_premiums

Compare tokenized US stock pool prices against Chainlink feeds on Robinhood Chain to see each token's premium percentage and feed age, free and without a key.

Instructions

What tokenized US stocks cost on Robinhood Chain against their Chainlink price right now: pool price, Chainlink price, the premium in percent and the feed's age, for NVDA, SPY, AAPL, TSLA, GOOGL, META and MSFT. Read from the chain, free, no key and no payment. Over a weekend the feeds stand still and the pools keep trading. usMarketOpen is true during the regular session, 09:30 to 16:00 New York time, Monday to Friday; it does not know exchange holidays or early closes. Prices are in USDG per token with each token's split multiplier applied. Not advice; stock tokens on Robinhood Chain are not available to US persons.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses read-only, free, keyless, payment-free access; that prices are denominated in USDG per token with each token's split multiplier applied; that weekend feed staleness makes premiums misleading; and the precise semantics and known blind spots of the usMarketOpen flag (no exchange holidays or early closes). It also adds a legal restriction on who may use the data, which is exactly the kind of context structured fields cannot convey.

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?

Front-loaded with the core 'what it costs right now' statement followed by the returned fields, then caveats and units. Every sentence carries information, though the market-hours sentence is dense and the legal disclaimer adds length; for a zero-parameter tool the text is on the long side but not padded.

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, so the description must describe what comes back, and it enumerates the four returned values plus the usMarketOpen flag, their units, and their interpretation caveats. Combined with the access and staleness notes, an agent has everything needed to call this and read the result 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 there is nothing for the description to disambiguate; baseline is 4. The description instead spends its words on return-value semantics (fields, units, multiplier), which is valuable but belongs to a different dimension.

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 names a specific resource (tokenized US stocks on Robinhood Chain vs. their Chainlink price), a specific verb (read the current premium), the exact fields returned (pool price, Chainlink price, premium percent, feed age), and the exact token universe. An agent knows precisely what this tool yields without opening anything else.

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?

It clearly frames the use case as a right-now spot check ('right now') and states the access conditions: read from the chain, free, no key, no payment. It also flags the key caveat that weekend premiums are distorted because feeds stand still while pools keep trading, which is effectively a when-to-trust-it guideline. It does not name an alternative tool for historical premiums or per-token filtering, so it stops short of explicit when-not/alternatives guidance.

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