Skip to main content
Glama

Drop-in AI grounding context (DIFFERENTIATED)

ai_context
Read-only

Returns a system prompt + structured context block, scoped to one ticker. Drop it into OpenAI/Anthropic/any LLM SDK to ground your chatbot in current Deep Values data without months of plumbing. Bills 3 metadata units. (GET https://app.deepvalues.ai/api/v1/ai-context/{ticker}, e.g. https://app.deepvalues.ai/api/v1/ai-context/AAPL — 0.02 credits per call; works with no credentials up to 1 call(s)/day per address) Missing data? Call request_data.

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": {
      "ticker": "<ticker>"
    },
    "name": "ai_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.
token_budgetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses cost (3 metadata units, 0.02 credits per call), the unauthenticated rate limit (1 call/day per address), the underlying endpoint, and the exact response shape. These are exactly the operational facts an agent needs before invoking a metered network call.

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 core capability is front-loaded in the first sentence, with cost and access constraints packed efficiently into parentheses. It is dense but every clause carries an operational fact; the parenthetical is slightly overloaded but not wasteful.

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 two-parameter, no-output-schema tool, the description covers what comes back (system prompt + context block), the cost, and the auth-free limit. The remaining hole is `token_budget` behavior and roughly what the structured block contains, which is a modest but real omission.

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 50%: `ticker` is well documented in the schema and reinforced by the path-substitution example in the description. `token_budget` is the more consequential knob — it controls how much context is returned — yet neither the schema nor the description explains its effect, so the definition adds little beyond structured fields here.

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 concrete verb and artifact: it returns a system prompt plus a structured context block scoped to one ticker, and states the intended consumer (OpenAI/Anthropic/any LLM SDK). No sibling tool produces LLM grounding context, so an agent can route to it without opening the 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?

It gives clear usage context — drop the output into an LLM SDK to ground a chatbot in current Deep Values data — and supplies a fallback path ("Missing data? Call `request_data`"). It does not state when an agent should prefer raw data tools like `fundamentals` instead, so there is a minor gap in alternative routing.

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