Skip to main content
Glama

Search redemptions

store_redemptions_search
Read-only

Search store redemptions by text, date range, pending status, or sort order to locate specific loyalty rewards for fulfillment. Supports pagination and filtered queries.

Instructions

Search store redemptions by text, with optional date range, pending filter and sort.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd of date range (ISO 8601)
fromNoStart of date range (ISO 8601)
sortNoSort field, e.g. createdAt or -createdAt
limitNoItems per page
offsetNoNumber of items to skip, for paging
searchNoText to search for
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.
pendingNotrue: only pending redemptions
searchByNoField to search in, e.g. username or item name (undocumented values)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond restating the filter inputs - nothing about pagination behavior, result ordering, or scope limits that would help the agent call it correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted clauses - the core action and its optional filters come first. It is efficient, though it is short enough that it omits potentially useful routing information.

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 read-only search tool with full schema coverage and no output schema, the definition is minimally adequate. The main gap is the absence of any differentiation from the sibling list/mine/get redemptions tools, which an agent needs in order to choose correctly.

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 all nine parameters are documented in the schema itself. The description mentions date range, pending filter and sort, but this only echoes fields the schema already explains, adding no syntax or semantic detail beyond it. Baseline 3 applies.

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?

States a specific verb ('Search') and resource ('store redemptions') plus the filter dimensions it supports. However it does not differentiate itself from close siblings like store_redemptions_list or store_redemptions_mine, leaving the agent to infer whether search is a filtered list or a distinct capability.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative. With store_redemptions_list, store_redemptions_mine and store_redemptions_get all present, no routing signal is provided to select this tool over them.

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