Skip to main content
Glama

list_resources

Filter and retrieve catalog resources using structured queries, exact matches, and logical conditions. Supports pagination and sorting for precise results.

Instructions

List catalog resources with advanced filtering capabilities.

This endpoint provides precise control over resource queries using structured filters.
Use this when you need exact matching, specific field filtering, or complex queries.

Args:
    filter: FilterOperand (field or logical) for filtering resources
    sort: SortConfig for ordering results
    page: Page number for pagination (default: 1)
    truncate_length: Maximum characters for text fields in results (default: 150)

Returns:
    Paginated list of resources matching the filter criteria

Filter Examples:

    # Single condition - title contains
    filter = {"operator": "contains", "field": "title", "value": "order_lines"}

    # Single condition - entity type
    filter = {"operator": "exact", "field": "native_type", "value": "table"}

    # Find all columns of a specific table
    filter = {"operator": "exact", "field": "parent_id", "value": "table-id-123"}

    # Multiple conditions with AND
    filter = {
        "operator": "and",
        "operands": [
            {"operator": "exact", "field": "native_type", "value": "table"},
            {"operator": "contains", "field": "title", "value": "customer"}
        ]
    }

Sort Examples:

    # Sort by title ascending
    sort = {"field": "title", "order": "asc"}

    # Sort by external_usage descending (most popular first)
    sort = {"field": "external_usage", "order": "desc"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter dictionary for filtering resources. Can be either a field filter or logical filter. Field filter example: {"operator": "exact", "field": "title", "value": "my_table"} Logical filter example: {"operator": "and", "operands": [{"operator": "exact", "field": "native_type", "value": "table"}, {"operator": "contains", "field": "title", "value": "order"}]} PARENT/CHILD RELATIONSHIPS (COMMON PATTERN): - Filter by parent_id to find ALL columns of a table: {"operator": "exact", "field": "parent_id", "value": "table-id-123"} Available field operators: "exact", "contains", "in", "is_set" Available logical operators: "and", "or", "not"
sortNoSort configuration dictionary for ordering results. Example: {"field": "title", "order": "asc"} With tie breaker: {"field": "updated_at", "order": "desc", "tie_breaker": {"field": "created_at", "order": "desc"}}
pageNoPage number for pagination
truncate_lengthNoMaximum characters for text fields in results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details the tool's behavior: listing with filtering, sorting, pagination, and truncation. Filter examples and sort examples are given. No side effects are mentioned, but as a list operation, none are expected.

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

Conciseness3/5

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

The description is long with extensive examples. While valuable, it could be more concise. The 'Args:' section largely repeats schema information. The structure is logical, but the length could be reduced without losing clarity.

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

Completeness5/5

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

Given the tool's complexity (4 parameters, filtering, sorting, pagination) and the presence of an output schema, the description is comprehensive. It covers all needed use cases with examples, making it fully adequate for an AI agent.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value beyond the schema, especially for complex parameters. It provides multiple filter examples (including parent/child relationships) and sort examples, which help an AI agent construct correct parameters. For page and truncate_length, it reinforces defaults already in schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List catalog resources with advanced filtering capabilities,' specifying the action (list) and resource (catalog resources). It distinguishes itself from siblings like get_resource (single resource) and search_data_assets (broader search) through the description.

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

Usage Guidelines4/5

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

The description explicitly says 'Use this when you need exact matching, specific field filtering, or complex queries,' providing clear guidance on when to use. It does not mention when not to use or direct alternatives like get_resource, but the context of sibling tools is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mbrummerstedt/secoda-analysis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server