Skip to main content
Glama

Get case risks

get_risks

Retrieves evidence-linked risks for one company, research subject, investment case or the explicitly selected released corpus. Returns recorded severity, lifecycle status, supporting evidence and unknown assessments. Useful for investigating a thesis's downside and invalidation conditions. Filter by investor, source, publication dates, status or severity. Empty filtered results reflect available assessed coverage; unknown risks remain separate. 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_risks"
  }
}

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.
severityNo
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

A3.9/5.0
Behavior4/5

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

Despite annotations already declaring destructiveHint=false and openWorldHint=false, the description adds real behavioral context: cursor pagination requiring unchanged filters, the meaning of empty filtered results as coverage limits, the separation of unknown risks, and cost ('account allowance or prepaid credit'). The billing note is especially valuable given readOnlyHint=false. It does not describe rate limits or response shape, which keeps it 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?

Eight short sentences with no filler, and the core identification (what is retrieved, for which scope) is front-loaded before filters, pagination, and billing notes. The mid-list sentence about empty results and unknown risks is slightly dense but still earns its place.

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 16-parameter paginated read tool, the description covers scope, filtering, pagination continuation, billing, and result semantics, and an output schema exists so return-value details are not needed. The remaining gap is the undocumented identifier and temporal parameters, which matters at this parameter count.

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 16 parameters and only 19% schema description coverage, the description carries a heavy burden; it compensates for some by mapping the filter dimensions (investor, source, published_from/published_through, object_status, severity) and explaining cursor reuse. It says nothing about as_of, limit, corpus, ticker, entity_id, belief_id, or person_id semantics, leaving roughly half the surface undocumented in both places.

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 description opens with a specific verb and resource (retrieves evidence-linked risks) and enumerates the four scopes the tool accepts: company, research subject, investment case, or released corpus. It is clearly distinct from siblings like get_catalysts or get_brief by naming 'risks' as the resource, though it never explicitly contrasts itself with those tools.

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 ('investigating a thesis's downside and invalidation conditions') and tells the agent how to narrow results with investor, source, date, status and severity filters. It stops short of naming alternatives or stating when NOT to use it, so it sits at clear-context-without-exclusions rather than full routing 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.