Skip to main content
Glama
tspvivek

Baasix MCP Server

by tspvivek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baasix_list_items

Retrieve items from any collection with advanced filtering, sorting, pagination, relations, and aggregation. Use operators like eq, contains, in, and geospatial to pinpoint data.

Instructions

Query items from a collection with powerful filtering, sorting, pagination, relations, and aggregation.

FILTER OPERATORS (50+):

  • Comparison: eq, neq, gt, gte, lt, lte

  • String: contains, icontains, startswith, endswith, like, ilike, regex

  • Null: isNull (true/false), empty (true/false)

  • List: in, nin, between, nbetween

  • Array: arraycontains, arraycontainsany, arraylength, arrayempty

  • JSONB: jsoncontains, jsonhaskey, jsonhasanykeys, jsonhasallkeys, jsonpath

  • Geospatial: dwithin, intersects, contains, within, overlaps

  • Logical: AND, OR, NOT

DYNAMIC VARIABLES:

  • $CURRENT_USER: Current user's ID

  • $NOW: Current timestamp

  • $NOW-DAYS_7: 7 days ago

  • $NOW+MONTHS_1: 1 month from now

FILTER EXAMPLES:

  • {"status": {"eq": "active"}}

  • {"AND": [{"price": {"gte": 10}}, {"price": {"lte": 100}}]}

  • {"tags": {"arraycontains": ["featured"]}}

  • {"author_Id": {"eq": "$CURRENT_USER"}}

  • {"category.name": {"eq": "Electronics"}} (relation filter)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort field and direction (e.g., "createdAt:desc", "name:asc")
limitNoItems per page (default: 10, use -1 for all)
fieldsNoFields to return. Use ["*"] for all, ["*", "relation.*"] to include relations
filterNoFilter criteria using operators like eq, neq, gt, gte, lt, lte, contains, in, between, etc.
searchNoFull-text search query
groupByNoFields to group by for aggregation
aggregateNoAggregation functions: {alias: {function: "sum|avg|count|min|max", field: "fieldName"}}
collectionYesCollection name
searchFieldsNoFields to search in (e.g., ["name", "description"])
relConditionsNoFilter conditions for related records: {"reviews": {"approved": {"eq": true}}}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It does so by documenting filter operator families, dynamic variables like $CURRENT_USER and $NOW, and concrete filter examples, which disclose how the query behaves beyond the schema. It does not mention auth, rate limits, or side effects, but the 'Query' framing makes the read-only nature reasonably clear.

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

Conciseness5/5

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

The description is long, but it is densely structured with clear sections for operators, dynamic variables, and examples. Every section adds operational value, and the one-sentence summary is front-loaded, making the length appropriate for a tool with 11 parameters and complex query semantics.

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 tool with 11 parameters, no annotations, and no output schema, the description covers query construction well but omits the response shape, pagination metadata, and any explicit relationship to sibling sort behavior. An agent may invoke the tool correctly but lacks a complete picture of what the returned payload will look like.

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%, so the baseline is 3, but the description adds substantial meaning to the filter and relConditions parameters by enumerating operator groups, dynamic variables, and real filter examples. This goes well beyond the schema's terse parameter descriptions and directly helps an agent construct valid complex queries.

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 clearly states the operation ('Query items from a collection') and its major capabilities (filtering, sorting, pagination, relations, aggregation), so the purpose is obvious. It does not explicitly disambiguate from sibling tools like baasix_get_item or baasix_sort_items, though 'list_items' and the query framing imply the distinction.

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 gives clear context for when to use the tool: querying and listing items from a collection with complex filters, pagination, and relations. It does not provide explicit when-not-to-use guidance or name alternatives, but the rich filter/operator documentation makes the intended usage readily apparent.

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