Baasix MCP Server

baasix_get_item

Retrieve a single item by ID from a Baasix collection, optionally including related data. Specify fields to return for precise record fetching.

Instructions

Get a specific item by ID from a collection, optionally including related data

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>",
      "id": "<id>"
    },
    "name": "baasix_get_item"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Item ID (UUID)
`fields`	No	Fields to return. Use ["", "relation."] to include relations
`collection`	Yes	Collection name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Aug 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description is the only safety signal. 'Get' clearly indicates a read-only retrieval, and 'optionally including related data' adds behavioral context beyond the schema. It does not mention not-found behavior or auth requirements, but the read operation carries low risk.

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?

One sentence with no filler; every phrase conveys the operation's scope and the optional relation feature. It is well front-loaded and easy to parse.

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

Completeness4/5

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

For a simple read tool, the schema plus the description covers invocation. Return format and not-found behavior are not described and no output schema exists, so agents must infer the response shape, but the core call is unambiguous.

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?

All three parameters are documented in the schema with 100% coverage, so the baseline is 3. The description repeats the conceptual role of id, collection, and fields but adds no syntax or default details beyond what the schema already provides.

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?

States a clear verb+resource: 'Get a specific item by ID from a collection'. The qualifier 'specific... by ID' distinguishes it from baasix_list_items, though it does not name a sibling explicitly.

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 'by ID from a collection' gives clear context for when to retrieve a single item, but it does not explain when to prefer baasix_list_items for multiple results or when to include related data. Usage is implied rather than explicitly contrasted with alternatives.

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

Deploy Server