Skip to main content
Glama

crashtestyourstrategy

List investment theses (catalog discovery)

list_investment_theses
Read-onlyIdempotent

USE WHEN you want to browse the investment-thesis case studies. Each entry is a descriptive case study pairing an economic framework with a rule-based portfolio and its stress evidence. Returns one compact summary per thesis (slug, title, one-liner, tags, risk tiers, framework summary, headline finding). Full detail: get_investment_thesis(slug). Descriptive, not advisory; the agent decides suitability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_investment_theses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real value beyond that by previewing the compact return shape and stating 'Descriptive, not advisory; the agent decides suitability' — a behavioral framing that stops the agent from treating outputs as recommendations.

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?

The trigger condition is front-loaded in the first clause, followed by entry definition, return shape, and the escalation sibling — each sentence carries distinct information. The parenthetical field list is dense but readable and not redundant padding.

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?

With zero params, full annotation coverage, and an output schema in place, the only remaining burdens are purpose, routing, and advisory framing — all addressed. An agent can call this correctly without opening any other field.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing to disambiguate. The description correctly conveys that this is an unfiltered catalog listing, which is the only parameter-adjacent fact an agent needs.

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 opens with a specific verb and resource ('browse the investment-thesis case studies') and clarifies what each entry is — a case study pairing an economic framework with a rule-based portfolio and stress evidence. It also distinguishes itself from the sibling get_investment_thesis by framing this as the catalog/list level versus full detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('USE WHEN you want to browse...') and names the alternative path ('Full detail: get_investment_thesis(slug)'), so the agent knows exactly which tool to pick for summary vs. detail. No ambiguity about when to invoke it is left.

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.