Skip to main content
Glama
Sign In

Stock Market Data MCP

by io.github.FoundryNet
OverviewDiscussionsAdmin

Daily Brief

daily_brief

Get the curated daily market brief — the day's top gainers and losers, most active names by volume, sector performance, and notable 52-week highs/lows, in one package. Each brief carries a MINT provenance attestation so a buyer can verify it was produced by this server, unaltered.

PAID: $20 USDC per brief. Defaults to today (UTC); a brief expires at the next midnight UTC. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=. An fnet_ Bearer key bypasses payment.

Input Schema

NameRequiredDescriptionDefault
dateNobrief date YYYY-MM-DD (default today, UTC).
agent_idNostable id for your agent (scopes the free-tier counter).
payment_txNoSolana tx signature, when re-calling after a 402 (x402 rail).
stripe_tokenNoStripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to x402). Can also be supplied via the X-Stripe-Token header.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / payment_tx / description
      Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)."
    • addedInput schema / properties / stripe_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does it well: discloses the $20 USDC price, the exact 402 recovery procedure (pay memo, re-call with SAME args plus payment_tx), the Stripe alternative path, and expiry semantics. It also explains the MINT provenance attestation, which is unexpected behavior an agent could not infer.

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?

Two tight blocks: what you get first, then cost and payment recovery. No filler, and the highest-value constraint (paid, per-brief) is front-loaded rather than buried.

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?

An output schema exists, so return values need not be described, and the description covers the money path thoroughly. The one gap is the free-tier counter tied to agent_id, which only the schema mentions; for a paid tool that is a notable omission but not disqualifying.

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 all four parameters are already documented, giving a baseline of 3. The description does add one piece of semantics beyond the schema — that payment_tx must be paired with identical arguments on retry — but says nothing about agent_id's free-tier scoping or stripe_token, which the schema handles alone.

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?

States a specific verb and resource ('Get the curated daily market brief') and enumerates the actual payload (gainers/losers, volume leaders, sector performance, 52-week extremes). That inventory of contents distinguishes it from quote, screener, and sector_performance without opening any schema.

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?

Gives clear operating context: defaults to today (UTC), expiry at next midnight UTC, the 402 pay-and-retry loop, and the fnet_ Bearer bypass. It stops short of naming when to reach for brief_summary or batch_quote instead, so the alternative-selection guidance is missing.

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

All Stock Market Data MCP 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