Skip to main content
Glama

Stock and crypto returns by market regime

lookup_symbols
Read-onlyIdempotent

How has this stock or crypto typically done in markets like today's? Returns, for one stock or crypto symbol per call (any US stock, plus the covered crypto list), its typical return and how often it rose over 1 to 12 months from the current regime. Stocks add sensitivity versus the S&P 500 and up to 5 peer symbols. A symbol with no price data is free, not covered. $0.01 per call in USDC on Base, Polygon or Solana (x402). Settled figures, updated after each US close (coins daily). The same figures as the symbol's page on regimecard.com. Useful when an agent needs stock returns by market regime or crypto returns by market regime for one holding.

Input Schema

NameRequiredDescriptionDefault
symbolNoOne stock or crypto symbol: any US stock, or a coin on the covered crypto list, for example "NVDA" or "BTC". Upper or lower case. One symbol per call.
symbolsNoThe earlier form of the same input: a list with exactly one stock or crypto symbol, for example ["NVDA"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / description
      Added value: +"A JSON object with exactly one field: symbol, or the earlier symbols with one entry. One symbol per call. A second symbol is a second call."
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "required": [
      +      "symbol"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "symbols"
      +    ]
      +  }
      +]
    • addedInput schema / properties / symbol
      Added value: +{
      +  "description": "One stock or crypto symbol: any US stock, or a coin on the covered crypto list, for example \"NVDA\" or \"BTC\". Upper or lower case. One symbol per call.",
      +  "examples": [
      +    "NVDA",
      +    "XLK",
      +    "BTC"
      +  ],
      +  "maxLength": 10,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / symbols / description
      Previous value: -"Stock or crypto symbols, for example [\"NVDA\", \"XLK\", \"BTC\"]. At most 20. Upper or lower case. Repeats are answered once."New value: +"The earlier form of the same input: a list with exactly one stock or crypto symbol, for example [\"NVDA\"]."
    • changedInput schema / properties / symbols / examples
      Previous value: -[
      -  [
      -    "NVDA",
      -    "BTC",
      -    "ZZZZ"
      -  ]
      -]New value: +[
      +  [
      +    "NVDA"
      +  ]
      +]
    • removedInput schema / properties / symbols / items / examples
      Removed value: -[
      -  "NVDA",
      -  "XLK",
      -  "BTC"
      -]
    • changedInput schema / properties / symbols / maxItems
      Previous value: -20New value: +1
    • removedInput schema / required
      Removed value: -[
      -  "symbols"
      -]
  2. Changed4 schema fields changed
    • changedInput schema / properties / symbols / description
      Previous value: -"Stock or crypto symbols, for example [\"NVDA\", \"XLK\", \"BTC\"]. At most 20."New value: +"Stock or crypto symbols, for example [\"NVDA\", \"XLK\", \"BTC\"]. At most 20. Upper or lower case. Repeats are answered once."
    • addedInput schema / properties / symbols / examples
      Added value: +[
      +  [
      +    "NVDA",
      +    "BTC",
      +    "ZZZZ"
      +  ]
      +]
    • addedInput schema / properties / symbols / items / description
      Added value: +"One stock, ETF or crypto symbol."
    • addedInput schema / properties / symbols / items / examples
      Added value: +[
      +  "NVDA",
      +  "XLK",
      +  "BTC"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, but the description adds substantial behavior they don't: a per-call price of $0.01 in USDC on Base, Polygon or Solana via x402, a free result when a symbol has no price data, freshness guarantees (updated after each US close, coins daily), and the authoritative source (the symbol's page on regimecard.com). It also repeats the hard constraint of one symbol per call, which is the key operational trait.

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

Conciseness3/5

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

It is front-loaded with the right framing question and every paragraph carries real information (coverage, price, freshness). But the second sentence is grammatically tangled ('Returns, for one stock or crypto symbol per call ..., its typical return and how often it rose') and the peer-sensitivity clause is embedded ambiguously rather than separated as return-value detail.

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 paid, read-only lookup with no output schema, the description covers coverage limits, pricing, freshness and response substance well enough to call it correctly. The only real gap is that the stock-specific extras (S&P 500 sensitivity, peer comparison) are mentioned without saying they are part of the returned figures, leaving mild ambiguity about the output.

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 both the symbol scalar and the legacy single-element symbols array are already documented with examples and length limits. The description reinforces 'one symbol per call' but adds no new meaning; the phrase 'up to 5 peer symbols' sits oddly next to a schema that forbids a second symbol and could momentarily confuse an agent into thinking peers are passable inputs.

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 a concrete verb and resource: typical returns and frequency of gains over 1–12 months for one symbol conditioned on the current market regime. It is clearly scoped to one symbol per call with US stocks and a covered crypto list. It does not differentiate itself from the sibling crypto_regime, so an agent cannot tell from the text alone which one to pick.

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?

Usage is implied by the closing line ('Useful when an agent needs stock returns by market regime or crypto returns by market regime for one holding'), which gives a reasonable trigger case. However, there are no explicit exclusions, no guidance on when to prefer crypto_regime or stress_gate, and no note on what to do for a symbol not on the covered crypto list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources