Skip to main content
Glama
Sign In
Baasix MCP Server

Baasix MCP Server

by tspvivek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baasix_sort_items

Reorder items in a collection by moving a specified item before a target item, updating the sort order.

Instructions

Sort items within a collection (move item before/after another)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>",
      "item": "<item>",
      "to": "<to>"
    },
    "name": "baasix_sort_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesID of target item to move before
itemYesID of item to move
collectionYesCollection name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.5/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden. It discloses only the core move/sort behavior and does not state whether the reorder is permanent, whether permissions are required, how other items are affected, or what the response/error behavior looks like. For a mutating tool this is a significant gap.

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 concise sentence that front-loads the verb and resource and adds a helpful clarifying parenthetical. There is no wasted text.

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?

The schema covers all required parameters, but the description does not clarify how 'after' should be achieved given that the 'to' parameter only mentions 'move before.' It also lacks return/error behavior and mutation effects. For a simple three-parameter tool, this is adequate but has clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline applies. The description adds only the general 'before/after' relationship between item and to, without providing additional format, constraint, or behavioral detail beyond the schema. The 'after' behavior is not represented by any parameter.

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 states a specific verb and resource: 'Sort items within a collection,' and clarifies the mechanism with 'move item before/after another.' This clearly distinguishes it from sibling tools like add_index or item CRUD operations.

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

Usage Guidelines3/5

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

The phrase 'Sort items within a collection' implies when it should be used, but there is no explicit guidance on when to prefer this over alternatives or when not to use it. It does not name sibling tools or exclusions.

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