Skip to main content
Glama

crashtestyourstrategy

Get one investment thesis (full case study)

get_investment_thesis
Read-onlyIdempotent

USE WHEN you want the full framework, portfolio and stress evidence of one thesis slug. Returns the framework (pillars with [E]/[M]/[K] evidence grades, falsifiers), the rule-based portfolio (asset blocks x conservative/balanced/offensive weights + sizing rationale) and the stress evidence (per-tier backtest, per-regime drawdown, historical episodes, claim verdicts marked by whether their rule was pre-registered, hedge behaviour). Slugs: list_investment_theses. Descriptive, not advisory; the agent decides suitability.

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": {
      "slug": "<slug>"
    },
    "name": "get_investment_thesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThesis slug — valid values: list_investment_theses() or get_started.
sectionsNoOptional subset of ['framework', 'evidence', 'portfolio', 'bridge'] to return (default: all; framework and evidence are about 8k characters each, portfolio about 2k). The thesis identity, disclaimer and `holdings` are always included; `section_sizes` lists what each section would cost.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / sections
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional subset of ['framework', 'evidence', 'portfolio', 'bridge'] to return (default: all; framework and evidence are about 8k characters each, portfolio about 2k). The thesis identity, disclaimer and `holdings` are always included; `section_sizes` lists what each section would cost.",
      +  "title": "Sections"
      +}
    • changedInput schema / properties / slug / description
      Previous value: -"Thesis slug — discover valid values via list_investment_theses()."New value: +"Thesis slug — valid values: list_investment_theses() or get_started."
  2. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Thesis slug — discover valid values via list_investment_theses()."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered; the description adds genuinely new behaviour — the thematic breakdown of the payload, evidence-grade conventions, pre-registration markers, and the 'descriptive, not advisory; the agent decides suitability' framing. Because an output schema exists, the long return-content enumeration is partly redundant, which keeps this from a 5.

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 activation clause, followed by a single returns sentence and a closing positioning statement; no filler. The middle sentence is a dense enumeration that is harder to scan than a short list, but every element carries information.

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?

Given a rich output schema, full annotation set, and 100% schema coverage, the description supplies everything left: when to use it, how to get a slug, what thematic content to expect, and the descriptive-not-advisory stance. Nothing an agent needs to call it correctly is missing.

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% and both parameters are already documented, including the slug source and the section-subset semantics with sizes. The description adds only the framing 'one thesis slug', which is largely duplicative — baseline 3 applies.

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 precise verb+resource+scope: fetch the full framework, portfolio and stress evidence for one thesis slug. It explicitly names the sibling (list_investment_theses) used for slug discovery, so an agent can distinguish it without opening either 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?

The 'USE WHEN you want the full ... of one thesis slug' clause gives a clear activation condition, and it routes slug lookup to list_investment_theses. It does not say when to prefer a lighter alternative (e.g. partial sections or another dossier-style tool), so it stops short of full when/when-not guidance.

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.