Skip to main content
Glama

rex_api_list

Retrieves all API methods exposed by the server, each labeled with its rex-mcp policy class, to help you identify callable operations and access constraints.

Instructions

API methods the server offers, each tagged with its rex-mcp policy class.

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_api_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one useful behavioral fact — every returned method is tagged with its policy class — but says nothing about whether the call is read-only (implied but unstated), authentication requirements, ordering, or whether the catalog is static or filtered by caller permissions.

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 short clause with no filler, and the most important information (what is returned) comes first. It is a noun phrase rather than a full sentence, which makes it slightly less self-explanatory than it could be at no extra length cost.

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?

With no output schema available, the description bears responsibility for describing the return value, and it only partially does so: it mentions the policy-class tag but not the other fields an entry likely carries (method name, description, parameters). For a simple zero-param listing tool this is adequate but leaves a real gap.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline for a no-param tool applies. Nothing in the description conflicts with the empty schema.

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 precisely: API methods the server offers, plus the metadata attached to each entry (its rex-mcp policy class). That is clearly distinct from rex_api_call (invoke) and rex_api_describe (detail on one method). It falls short of a 5 because it never explicitly names the enumeration verb or points at those siblings.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no statement of prerequisites or follow-up steps (e.g. 'call rex_api_describe for details on a listed method'). An agent must infer that this is a discovery entry point purely from the word 'list' and the sibling names.

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