Skip to main content
Glama

search_risk_cases

Read-only

Retrieve bounded historical official safety-alert evidence, separated by source; not a current-law or product approval. For a case follow-up use its full returned official URL; never digits alone.

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": {
      "query": "<query>"
    },
    "name": "search_risk_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
required_groupsNo
limit_per_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, closed-world), and the description adds meaningful context beyond that: results are bounded and grouped per source, are historical rather than current-law, and case follow-up requires the full returned URL rather than a bare number. It still does not describe what a result record contains or how sources are separated in the response.

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?

Two compact sentences with no filler, and the core scope statement is front-loaded ahead of the caveat and the follow-up rule. The terseness occasionally costs clarity ('bounded', 'separated by source'), but nothing is redundant.

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

Completeness2/5

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

For a three-parameter tool with no output schema and zero schema descriptions, the definition leaves the crucial parameters unexplained and does not describe the per-source grouping it advertises. The legal-disclaimer and citation-rule content is good, but an agent still cannot tell what to put in required_groups or what a bounded result set looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with three parameters, so the description must compensate. 'Bounded' only faintly gestures at limit_per_source (capped at 2), and neither 'required_groups' nor 'query' is explained at all, leaving two of three parameters with no interpretive help anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Retrieve ... official safety-alert evidence') and adds scope qualifiers ('bounded', 'historical', 'separated by source'), so the general domain is clear. However, the phrasing is densely compressed and never says concretely what a 'risk case' is or how it differs from the sibling search_legal_sources beyond the negative 'not current-law'.

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

Usage Guidelines3/5

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

It gives a negative boundary ('not a current-law or product approval') and a follow-up rule ('use its full returned official URL; never digits alone'), which are useful usage cues. It does not say when to prefer this tool over the sibling legal-sources search, so routing between the two remains implicit.

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