Skip to main content
Glama

Swarm Ecology register

lookup_case

Read-only

Returns a register case by id, or up to five cases whose title or summary contains every word of a query.

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": "lookup_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA case id, such as SE-2026-0001.
queryNoWords to find in a case title or summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: results are capped at five, matching is conjunctive ("every word"), and the searched fields are title and summary. It omits any statement of ordering, empty-result behavior, or precedence between the two parameters.

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?

A single sentence with the primary mode stated first and the fallback search mode second, with no filler or repetition of schema details.

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?

With no output schema, the description usefully discloses the five-result cap, which the agent otherwise could not know. For a two-mode tool with optional parameters and no annotations about result shape, however, it should also address behavior when both parameters are present, when neither is, and what a miss returns.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by stating that query matching requires all words to appear (the schema only says "Words to find") and by implying id is an exclusive alternative to query. It still leaves the both/neither case ambiguous.

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 names a specific verb and resource ("Returns a register case") and spells out two distinct modes: exact id lookup and a capped text search. It does not contrast itself with the sibling search_glossary / search_library tools, so an agent must still infer which tool covers register cases versus glossaries or libraries.

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?

Usage is only implied by the two modes: pass id for a direct fetch, pass query for a text match. There is no statement about which mode takes precedence if both are supplied, nor what happens if neither is supplied, and no explicit routing away from the sibling search tools.

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