Skip to main content
Glama

case_search

Searches a case's entities, sources, observations, and relationship text to locate evidence; uses full-text relevance ranking when available and substring matching as fallback.

Instructions

Search a case's entities, sources, observations, and relationship text.

Uses an FTS5 full-text index when available (relevance-ranked, word-based matching); falls back to substring LIKE matching otherwise.

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

Input Schema

NameRequiredDescriptionDefault
caseYes
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose genuinely useful matching semantics: relevance-ranked word matching versus substring LIKE fallback, which changes result quality and query behavior. However, it omits permissions, error behavior, what the default limit of 30 does, and what results look like, leaving meaningful gaps.

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?

Two tightly written sentences with the core purpose front-loaded and the matching-engine detail trailing as supporting context. Nothing is padded or redundant.

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 three-parameter search tool with no annotations and no output schema, the description covers the search mechanism but not the essentials an agent needs: the case identifier format, which fields are actually searched, the result shape, and the effect of the limit parameter. It is serviceable but leaves the caller to infer too much.

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% and the description explains none of the three parameters: it never clarifies whether 'case' is an ID or name, what syntax 'query' accepts, or how 'limit' is applied. The only parameter-adjacent value is the hint that queries are word-based under FTS5 and substring-based otherwise, which partially informs how to phrase the query.

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 gives a specific verb (Search) and enumerates the exact resource scope: a case's entities, sources, observations, and relationship text. This clearly distinguishes it from case-wide or external search tools like case_list or web_search by making the in-case, text-matching scope explicit.

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?

The description implies usage by stating it searches within a case, but it offers no explicit when-to-use versus alternatives such as case_list or case_graph, and no conditions under which a different tool would be better. The FTS5-versus-LIKE note describes mechanics rather than selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.