Export all schemas as JSON to retrieve a complete backup or inspect your data model.
Export all schemas as JSON
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_export_schemas"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Export all schemas as JSON' and does not mention whether the operation is read-only, whether it returns a file or inline JSON, whether it requires authentication, or whether it has side effects. The output format is disclosed, but other behavioral context is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear, front-loaded sentence with no filler. Every word adds meaning: 'Export' indicates action, 'all schemas' defines scope, and 'as JSON' defines the format.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description is mostly sufficient: it communicates the action, scope, and format. It could be enriched by explaining what 'export' returns (e.g., an array vs. an object) and whether it includes relationships, but these are relatively minor gaps for such a simple operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 100%, so there is nothing for the description to add about input semantics. The mention of 'as JSON' provides some useful information about the output format, which partially compensates for the lack of an output schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Export'), a resource ('all schemas'), and an output format ('as JSON'). It clearly distinguishes itself from siblings like baasix_list_schemas (which likely lists metadata) and baasix_get_schema (singular) by emphasizing the bulk export of all schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as baasix_list_schemas, baasix_get_schema, or baasix_import_schemas. The description does not state any exclusions, prerequisites, or conditions, leaving usage entirely implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.