Skip to main content
Glama

resource_list

Read-only

Page through workspace resources with prefix filtering and pagination to browse and locate FiveM resources by name.

Instructions

Page through resources in the workspace

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The only behavioral addition is 'Page through', which signals paginated results, but it never explains the cursor mechanic, ordering, or result size behavior beyond the schema defaults.

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 seven-word sentence with no filler and the action front-loaded. It is efficient, though its brevity tips into under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no parameter documentation and only a one-line description, an agent cannot know the response shape, pagination protocol, or how prefix narrows results. For a listing tool with three undocumented parameters, this leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description carries the full burden and fails to meet it. 'Page through' loosely implies the after/limit pair but says nothing about cursor semantics or bounds, and the prefix filter is never mentioned at all.

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 verb phrase 'Page through' plus the resource 'resources in the workspace' tells an agent this is a paginated enumeration, which distinguishes it implicitly from resource_read (single read) and resource_create/edit/delete. It does not explicitly name any sibling or clarify what a 'resource' denotes in this system, so it stops short of a 5.

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 at all: nothing says to call this for browsing versus resource_read for fetching a specific one, or when to prefer resource_get_diagnostics. The agent must infer tool selection from the name alone.

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