Skip to main content
Glama

Redra

by io.github.sacrosaunt

Search settlements in a batch

search_settlements_batch
Read-onlyIdempotent

Run up to 50 independent settlement searches and deduplicate records across queries. Results include matched_query_indices, and executed_query_count reports the number of searches performed. Use when several unrelated search angles should be evaluated together.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queriesYesIndependent settlement searches. Each query retains logical-AND keyword semantics; unrelated alternatives belong in separate query objects.
max_total_resultsNoMaximum unique settlement records returned across the whole batch after cross-query deduplication. This caps output, not the number of independent searches performed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / SearchQuery / properties / proof_required / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "yes",
-      "no",
-      "optional",
-      "varies",
-      "unknown"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "yes",
+      "no",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / SearchQuery / properties / proof_required / description
      Previous value: -"Exact proof requirement: yes, no, optional, varies, or unknown."New value: +"Whether proof is required: yes, no, or unknown."
  2. Changed2 schema fields changed
    • changedInput schema / $defs / SearchQuery / properties / proof_required / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "yes",
-      "no",
-      "optional",
-      "unknown"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "yes",
+      "no",
+      "optional",
+      "varies",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / SearchQuery / properties / proof_required / description
      Previous value: -"Exact proof requirement: yes, no, optional, or unknown."New value: +"Exact proof requirement: yes, no, optional, varies, or unknown."
  3. Changed3 schema fields changed
    • changedInput schema / $defs / SearchQuery / properties / status / description
      Previous value: -"Claim lifecycle; defaults to open. Use all only when intentionally searching non-open lifecycle states as well."New value: +"Public lifecycle filter: open or upcoming. Defaults to open. Upcoming records are not yet claimable and belong in a separate watchlist."
    • changedInput schema / $defs / SearchQuery / properties / status / enum
      Previous value: -[
-  "open",
-  "closed",
-  "payment",
-  "unknown",
-  "all"
-]New value: +[
+  "open",
+  "upcoming"
+]
    • changedInput schema / properties / queries / description
      Previous value: -"Independent settlement searches. Use one query object per unrelated company, product, alias, alternative term, or search angle. Keywords inside each object still use logical AND."New value: +"Independent settlement searches. Each query retains logical-AND keyword semantics; unrelated alternatives belong in separate query objects."
  4. Changed4 schema fields changed
    • removedInput schema / $defs / SearchQuery / properties / status / anyOf
      Removed value: -[
-  {
-    "enum": [
-      "open",
-      "closed",
-      "payment",
-      "unknown"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / $defs / SearchQuery / properties / status / description
      Previous value: -"Claim lifecycle; defaults to open. Use null for all statuses."New value: +"Claim lifecycle; defaults to open. Use all only when intentionally searching non-open lifecycle states as well."
    • addedInput schema / $defs / SearchQuery / properties / status / enum
      Added value: +[
+  "open",
+  "closed",
+  "payment",
+  "unknown",
+  "all"
+]
    • addedInput schema / $defs / SearchQuery / properties / status / type
      Added value: +"string"
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint: true, destructiveHint: false, openWorldHint: false. The description adds: it deduplicates records across queries Eq. and reports executed_query_count. However, it does not mention partial-failure behavior, query-level limits, or what happens when max_total_results cap is hit. With annotations carrying the read-only safety profile, the description adds moderate behavioral context (deduplication and count reporting) but not rich detail on failure modes or output shape.

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?

Three sentences, no fluff easchjs. Clearly explains batch capability, result metadata, and when to use. Efficient.

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 batch tool, the description explains the core behavioral traits (deduplication, count reporting, cap) and when to use it. It doesn't describe result structure (e.g., grouped by query) but given the input schema richness and readOnly annotations, this is a solid comprehensive description. Could mention parallel independent behavior more, but the queries array description in schema covers it. Score 4.

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?

Schema coverage of parameters is high (all params documented in schema), so description adds limited incremental value. The description clarifies that max_total_results caps output but not the number of searches, which is a useful clarification that goes slightly beyond the schema. For the queries array parameter, it already says 'Independent settlement searches' and retains the AND semantics in the schema. Description adds dedup context for results but not parameter-level details. Baseline 3 is appropriate with the slight boost for clarifying max_total_results.

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?

Description accurately conveys purpose: run up to 50 settlement searches in one batch, dedupe results. It identifies the verb (search), resource (settlements), and mode (batch), clearly distinguishing itself from a single settlement search. It lacks an explicit sibling name reference, but the verb+resource+scope structure is clear enough to position it.

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

Usage Guidelines5/5

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

Description tells when to use: 'several search angles should be evaluated together' and the annotation 'openWorldHint: false' reinforces constrained usage. Explicitly contrasts with a single-search tool by mentioning independent queries and dedup. It does not state 'when NOT to use', but provides strong positive guidance and boundary (up to 50 queries) so an agent can decide to route batch vs single search.

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

All Redra toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: dataset metadata, single-record retrieval, batch retrieval, single search, and batch search. No overlapping boundaries or potential for misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_dataset_info, get_settlement, get_settlements, search_settlements, search_settlements_batch). Verbs and noun plurality are used logically and consistently.

Tool Count5/5

With exactly 5 tools, the server is well-scoped for its apparent purpose of settlement searching and retrieval. Each tool fills a necessary role without redundancy, making the count ideal.

Completeness5/5

The tool surface fully covers the read-only workflow: dataset-level info, targeted retrieval (single and batch), and search (single and batch). No obvious gaps for the domain, as update/create/delete operations are not implied by the server's purpose.

Resources