Skip to main content
Glama
Sign In

Redra

by io.github.sacrosaunt
OverviewDiscussionsAdmin

Get settlements

get_settlements
Read-onlyIdempotent

Return complete stored records and official source links for up to 20 settlement IDs produced by search.

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": {
      "settlement_ids": "<settlement_ids>"
    },
    "name": "get_settlements"
  }
}

Input Schema

NameRequiredDescriptionDefault
settlement_idsYesSettlement identifiers returned by search to retrieve together.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / settlement_ids / description
      Previous value: -"Settlement identifiers to retrieve together. Use this for every finalist from a broad scan before composing the final answer."New value: +"Settlement identifiers returned by search to retrieve together."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is clear. The description adds that it returns 'complete stored records and official source links', which indicates a richer response than a summary. This is useful context beyond annotations. No contradiction exists.

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?

The description is a single concise sentence, front-loaded with the primary purpose, and includes key constraints (up to 20 IDs). There is zero waste; every word contributes value.

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?

With one parameter (fully covered by schema), strong annotations, an output schema present, and a clear description, the tool is well documented. The description explains the use case ('produced by search') and the batch limit, which is sufficient. Minor gap: it doesn't mention error behavior or what happens if an ID is invalid, but given the presence of an output schema, this is acceptable.

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 description coverage is 100%, so the parameter 'settlement_ids' is well documented already. The description adds that these are 'produced by search' and 'to retrieve together', which reinforces the batch context, but it doesn't add new semantics beyond the schema's description. Baseline 3 is appropriate.

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 clearly states the tool returns complete stored records and official source links for up to 20 settlement IDs produced by search. The verb 'Return' is specific, the resource is 'settlements', and the scope ('up to 20') is defined. However, it doesn't explicitly distinguish from sibling 'get_settlement' (singular), though the pluralization and 'up to 20' partially imply a batch operation.

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 says 'produced by search', which implies this tool is used after search results are obtained, providing a context. However, it doesn't explicitly state when-not-to-use or mention alternatives like 'get_settlement' for single-record retrieval. The guidance is minimal but not misleading.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources