Skip to main content
Glama

rex_actions_list

Lists actions a Rex server offers (init.lua and block types) or those a client reports, helping you discover available actions before invoking them.

Instructions

Actions the server offers (init.lua and block types), or those a client reported with client.

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

Input Schema

NameRequiredDescriptionDefault
clientNo

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses the scope of listed actions but does not confirm that the operation is read-only, describe side effects, permissions, rate limits, or return format.

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?

The definition is a single front-loaded sentence with no filler, making it easy to scan. Its terseness borders on under-specification, but every phrase contributes to describing scope.

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?

Given the low complexity (one optional parameter, no output schema, no annotations), the description covers the basic scope but omits the return shape and clearer usage context. It is minimally adequate rather than complete.

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 0%, so the description must explain the single optional `client` parameter. It does indicate that `client` selects actions reported by a client, but it does not specify the expected client identifier format or fully clarify default behavior when omitted.

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 identifies the resource as 'actions' and distinguishes server-offered actions (init.lua and block types) from client-reported actions. It is clear enough to understand the tool's broad purpose, though it does not explicitly contrast itself with siblings like rex_api_list or rex_list.

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 implies the tool is used to list available actions and that the optional `client` parameter retrieves client-reported actions, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer usage from the name and parameter.

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