Skip to main content
Glama
Sign In
koble-mcp

koble-mcp

Official
by koblesystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebms_export

Exports an entire EBMS collection to CSV, Excel, or JSONL for large datasets and returns the file path, row count, columns, sample rows, and numeric aggregates instead of all rows.

Instructions

Read a whole EBMS collection to a file (CSV, Excel or JSONL) instead of into the conversation, for anything more than a few hundred rows: sales history, every product, all open lines. The server pages through it itself and returns only the file's path, the row count, the columns, five sample rows and min/max/sum of each numeric column — never the rows. Analyse the file with a script (pandas, duckdb) and read back only the aggregates; never write a script that calls EBMS. Count first with ebms_get (top 1). Select only the fields you need. Read-only.

Input Schema

NameRequiredDescriptionDefault
pathYesRequired. An entity set, e.g. ARINVDET, INVENTRY. Not a keyed path.
expandNo$expand, with a select inside, e.g. Details($select=INVEN,O_QUAN_VIS). Line _VIS fields read 0 unless read through the parent like this.
filterNo$filter, unencoded.
folderNoOnly a folder the user named: an existing one, not hidden and not koble's settings. Default: KOBLE_EXPORT_DIR, or 'Koble Exports' in the user's Documents (created if missing).
formatNoDefault csv.
selectYesRequired. $select, comma-separated. AUTOID is added if missing.
companyNoCompany, by ID or name as ebms_companies lists them. May be omitted only when one company is available.
explodeNoAn expanded collection, e.g. Details: one row per child, with the parent's fields repeated and the child's as Details.<FIELD>. Without it an expanded collection is JSON text in one cell.
maxRowsNoRefuse an export larger than this. Default 250000.
orderbyNoDefault AUTOID, so pages do not shift while being read; where EBMS refuses that sort, the server's own order is used and repeats are still removed by AUTOID (the result says ordered: false).
filenameNoFile name only. Default <company>-<entity>-<timestamp>. An existing file is never overwritten.
pageSizeNoRows per request. Default 500, or 25 with an expand. Lower it if a page times out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that the server pages internally, that it returns only path, row count, columns, five sample rows and numeric aggregates 'never the rows', that existing files are never overwritten, that ordering may fall back ('ordered: false'), and that it is read-only. That is substantive behavioral context beyond a bare verb.

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

Conciseness4/5

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

Front-loaded with the core purpose and the file-vs-conversation distinction before the mechanics. Dense but nearly every clause carries information; the dash-heavy style is slightly compressed but not padded.

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

Completeness5/5

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

No output schema exists, so the description must explain the return shape — and it does precisely (path, row count, columns, five samples, per-numeric min/max/sum). For a 12-parameter export tool this covers everything an agent needs to call it and interpret the result.

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% and the param descriptions already explain expand/explode examples, defaults and maxRows behavior, so the schema does the heavy lifting. The description reinforces field selection ('Select only the fields you need') but adds little parameter-level meaning beyond what the schema states. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Read a whole EBMS collection') plus the destination ('to a file (CSV, Excel or JSONL)') and explicitly contrasts with the alternative of reading into the conversation. An agent can distinguish this from ebms_get without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit selection criteria ('anything more than a few hundred rows'), names the prerequisite/alternative ('Count first with ebms_get (top 1)'), and describes the downstream workflow ('Analyse the file with a script... never write a script that calls EBMS'). When-to-use and when-not-to-use are both present.

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