Skip to main content
Glama
Sign In
IndigoProtocol/indigo-mcp

IndigoProtocol/indigo-mcp

Official
by IndigoProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_redemption_orders

Retrieve executed redemption orders from Indigo Protocol, optionally filtering by iAsset, to view completed redemptions and analyze protocol activity.

Instructions

Get executed redemption orders, optionally filtered by iAsset

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

Input Schema

NameRequiredDescriptionDefault
assetNo
limitNoMax number of records (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.1
    • addedInput schema / properties / asset
      Added value: +{
+  "enum": [
+    "iUSD",
+    "iBTC",
+    "iETH",
+    "iSOL",
+    "iEUR",
+    "iJPY",
+    "iADA"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / in_range
      Removed value: -{
-  "description": "Filter by price range",
-  "type": "boolean"
-}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max number of records (default 100)",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "number"
+}
    • removedInput schema / properties / timestamp
      Removed value: -{
-  "description": "Unix timestamp in milliseconds",
-  "type": "number"
-}
  2. First observedv0.2.14

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Get' implies a safe read operation and 'executed' adds useful status filtering, but the description does not disclose return format, pagination behavior, or ordering. It is not misleading, but it is minimal.

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 front-loaded sentence with no filler. It communicates the core action, the resource, and the optional filter in minimal words.

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?

The tool is simple, has no output schema, and no annotations. The description covers the essential purpose and filter, but it does not mention return shape or clarify how it differs from the closely related get_redemption_queue tool, so the context is only minimally complete.

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 description coverage is 50%, and the description compensates by explaining that the asset parameter filters by iAsset. The limit parameter is already documented in the schema with a default and maximum. Together, all parameters have adequate semantic meaning.

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 resource ('executed redemption orders') and the action ('get'), and adds an optional filter by iAsset. It is specific enough to be distinguishable from most sibling tools, though it does not explicitly contrast with get_redemption_queue.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives such as get_redemption_queue. There are no preconditions, exclusions, or recommended contexts beyond the implicit fact that it returns executed orders.

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

Deploy Server

Other Tools