Skip to main content
Glama
Sign In
Baasix MCP Server

Baasix MCP Server

by tspvivek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baasix_realtime_collections

Retrieve realtime-enabled collections and their action configurations to manage realtime subscriptions.

Instructions

Get list of collections with realtime enabled and their action configurations

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Get list' signals a read-only retrieval and the description adds useful scoping, but it does not disclose authentication needs, edge-case behavior such as an empty result, or any other side effects or limitations.

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 a single front-loaded sentence with no filler: the verb comes first, followed by the resource, the distinguishing filter, and the included data. Every word earns its place.

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?

There is no output schema and no annotation coverage, so the description is the agent's only guide to what the tool returns. It names the main output concepts but leaves the shape of 'action configurations' and any list-level behavior unspecified, which is a moderate gap for an otherwise simple zero-parameter tool.

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 has zero parameters and the schema coverage is effectively complete, so there is no parameter detail for the description to add. The description still reinforces the fixed scope of the result set: only collections with realtime enabled and their action configurations.

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 the operation ('Get list'), the resource ('collections'), the filter ('with realtime enabled'), and the included data ('their action configurations'). This distinguishes it from siblings like baasix_realtime_status and baasix_realtime_config, which concern realtime status or configuration rather than listing the collections themselves.

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 explicit guidance about when to use this tool versus alternatives, no exclusions, and no mention of sibling tools. The use case is only implied by the description itself, so an agent must infer when this is the right call among the many related realtime and collection tools.

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