Skip to main content
Glama

Quillm

Create a dataset

create_dataset

Creates a named table that views read with useDataset(name). Define typed columns and a key: the column(s) that uniquely identify a row (e.g. ["month"], or ["date","campaign"]). The key makes updates idempotent: pushing a row with an existing key updates it instead of duplicating it. You can pass initial rows in the same call. Prefer tidy, raw-ish data (one row per month/day/entity with numeric columns) over pre-aggregated text; views compute totals and deltas themselves. Check get_workspace first: if a dataset with this data already exists, add to it with upsert_rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesColumn(s) that uniquely identify a row, e.g. ["month"] or ["date","campaign"].
nameYessnake_case, content + grain, e.g. "mrr_monthly", "ad_spend_daily". Permanent.
rowsNoInitial rows: [{"month": "2026-01", "mrr": 41200}, …].
columnsYesEvery column, the key columns included.
descriptionYesWhat one row represents and where the data comes from.
update_cadenceNoHow often this data is expected to be refreshed. The app flags the dataset as stale when overdue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not open-world), so the bar is lower. The description still adds real behavior: the `key` semantics and that pushing a row with an existing key updates rather than duplicates. It does not cover failure modes (duplicate name, 5000-row/60-column limits) that live only in the schema.

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 key contract, then the routing rule. Roughly five sentences, all relevant, though the tidy-data modeling advice is the one part that could be trimmed without losing invocation-critical information.

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?

With no output schema, the description carries the return-side burden and adequately conveys what the created artifact is and how it is consumed. Limits (row/column caps) and duplicate-name behavior appear only in the schema, leaving a small completeness gap for a 6-parameter mutation 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?

Schema description coverage is 100%, so 3 is the baseline. The description adds meaning beyond the schema: `key` as the uniqueness/idempotency contract and a modeling preference for tidy raw-ish numeric rows over pre-aggregated text, which shapes how `columns` and `rows` should be populated.

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 ("Creates a named table") and immediately frames the artifact's role ("that views read with useDataset(name)"). It further distinguishes itself from siblings by naming get_workspace and upsert_rows for the 'dataset already exists' case.

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?

Explicit routing: "Check get_workspace first: if a dataset with this data already exists, add to it with upsert_rows." It also gives positive guidance on when this tool is the right shape (new raw-ish data) versus pre-aggregated text.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.