Skip to main content
Glama

Manawa Terminal

Run DeepDive analysis

run_deepdive

Queue a full DeepDive suite for a stock using a monthly custom-run grant.

Prepaid search credits cannot pay for this. Free plans have 0 runs;
Basic has 10/month; Pro has 50/month. Re-running a ticker already
unlocked this month does not consume another grant. The call returns
as soon as the job is queued — do not poll.

Args:
    ticker: Stock symbol (e.g. "AAPL")
    force: Re-queue every chapter even when a current report exists.
        Use when on-file content is the wrong instrument (e.g. ZS
        Thesis written as soybeans).

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

Input Schema

NameRequiredDescriptionDefault
forceNo
tickerYes
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
      +  "default": false,
      +  "title": "Force",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses async behavior ('returns as soon as queued — do not poll'), quota consumption rules, and that re-running an unlocked ticker this month does not consume a grant. This is substantial behavioral context that annotations do not carry.

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 action, then quota rules, then the async note, then args. Every sentence is informational. The quota tier listing is slightly verbose but earns its place by defining eligibility.

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 non-destructive mutation tool with an output schema (so return values needn't be explained), the description covers triggering, quota gating, idempotency, async semantics, and both key parameters. The remaining gap is minor: no explicit alternative-tool routing.

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?

Schema coverage is only 33% (only strategy_id is documented in the schema), but the description supplies the missing meaning for ticker (with an example) and force (when to use it, with a concrete failure scenario). Together the schema and description cover all three parameters well.

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 first sentence gives a specific verb and resource: 'Queue a full DeepDive suite for a stock.' It is unambiguous what the tool does and clearly distinct from generic analysis siblings. It does not explicitly name a sibling it competes with, but no other DeepDive tool exists, so differentiation is implicit.

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 explains when-not: 'Prepaid search credits cannot pay for this' and the quota tiers that gate usage. It also gives a specific condition for using force (wrong-instrument on-file content). It stops short of naming an alternative tool for overlapping needs, but the context is clear.

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