Skip to main content
Glama

Get case catalysts

get_catalysts

Retrieves evidence-linked catalysts for one company, research subject, investment case or the explicitly selected released corpus. Returns recorded conditions, lifecycle status, dates and supporting evidence. Useful for checking which thesis events remain pending, were met or missed, or have been superseded. Filter by investor, source, publication dates or status. Unassessed conditions retain unknown status. Continue with the returned cursor and unchanged filters. Uses account allowance or prepaid credit.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_catalysts"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
limitNo
corpusNo
cursorNo
tickerNo
contextYesUser's research goal in one short sentence (max 300 characters); include relevant ticker and topic. Exclude names, contact/account/portfolio details, credentials and source text.
belief_idNo
entity_idNo
llm_modelYesYour model identifier, if known (e.g. gpt-6); otherwise leave unknown. Exclude credentials and private deployment names.
person_idNo
source_idNo
object_statusNo
published_fromNo
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
published_throughNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations it discloses two things the structured fields do not: that the call consumes account allowance or prepaid credit, and that unassessed conditions return an unknown status rather than being silently dropped. It also explains pagination continuity (reuse the cursor with unchanged filters), which matters because the annotations mark the tool non-idempotent. The return shape is left to the output schema, which is fair.

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?

Purpose is front-loaded, then return contents, then use case, then filters, then edge-case and pagination notes — a sensible ordering with little filler. The filter sentence is slightly vague about which parameter each filter maps to, which is the main place wording could be tightened rather than shortened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter tool with an output schema and existing annotations, the description covers return semantics, cost, and continuation adequately. What it lacks is the one thing an agent most needs before the first call: how to choose among the mutually exclusive identity parameters and what happens if none or several are supplied. That gap is significant given how many selector parameters exist.

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?

With only 20% schema description coverage across 15 parameters, the description has to carry weight — and it partially does, mapping scope language onto the identity parameters and calling out investor, source, publication-date and status filters. However, it never states that the entity selectors (ticker, entity_id, person_id, belief_id, corpus) are alternatives rather than combinable, nor does it explain object_status or as_of, which are the highest-risk inputs to misuse.

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 ("Retrieves evidence-linked catalysts") and immediately enumerates the four valid scopes (one company, research subject, investment case, or the released corpus). An agent can tell this apart from generic siblings like get_case or get_news 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 a concrete use case — checking which thesis events remain pending, were met, missed, or superseded — which tells the agent why it would reach for this tool. It stops short of naming a sibling to prefer when the user wants a full case narrative (get_case) or risk items (get_risks), so routing between adjacent tools is still partly inferred.

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.