Skip to main content
Glama
Sign In

Dock

by ai.trydock
OverviewDiscussionsAdmin

add_column

Append a single column to a workspace's table schema. Position is auto-computed as next-after-max so the contiguity invariant holds. Key collision (409) if a column with the same key already exists. Editor role required. Use this for per-column additions; use get_workspace_schema + update_surface with columns for full schema replacement or reordering. Multi-surface workspaces accept surface_slug to target a specific table sheet (use list_surfaces to enumerate); omit to fall through to the workspace's primary table surface.

Input Schema

NameRequiredDescriptionDefault
keyYesField name in row.data. Lowercase + underscores recommended; 1-64 chars.
slugYesThe workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace.
typeYesColumn type. See get_workspace_schema for examples.
labelYesHuman-readable header shown in the sheet.
widthNoOptional. Initial column width in px.
optionsNoRequired for `status` + `select` types. The allowed values shown in the dropdown.
descriptionNoOptional. Human-readable tooltip shown in the column header. Up to 4000 characters (the same limit update_surface applies).
surface_slugNoOptional. The slug of the specific table surface to add the column to. Omit on single-table workspaces; required on multi-table workspaces if you don't want the primary table surface (lowest position).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional. Human-readable tooltip shown in the column header."New value: +"Optional. Human-readable tooltip shown in the column header. Up to 4000 characters (the same limit update_surface applies)."
  2. Changed1 schema field changed
    • addedInput schema / properties / surface_slug
      Added value: +{
+  "description": "Optional. The slug of the specific table surface to add the column to. Omit on single-table workspaces; required on multi-table workspaces if you don't want the primary table surface (lowest position).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL — both resolve to the same workspace."New value: +"The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations, so the description carries the full burden, and it delivers real behavioral context: position is auto-computed as next-after-max to preserve a contiguity invariant, a 409 key collision surfaces if the key exists, and Editor role is required. It falls short of disclosing return value, rate limits, or what happens to existing rows when the column is added.

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?

Four dense sentences, each carrying distinct value: purpose, position invariant, error behavior, auth requirement, sibling routing, and surface targeting. Front-loaded with the core action and no filler.

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 mutation tool with no annotations and no output schema, it covers purpose, permissions, error semantics, and targeting well. The main gap is what the call returns (the created column representation), which an agent might want given no output schema is defined.

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 schema already documents all 8 parameters including surface_slug, options, and description. The narrative reinforces surface_slug's fallthrough behavior but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Append a single column to a workspace's table schema') and explicitly contrasts itself with siblings ('use get_workspace_schema + update_surface with `columns` for full schema replacement or reordering'). An agent can distinguish it from update_surface/add_column alternatives without opening a 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?

Names the alternative path and the condition that selects it (per-column additions vs. full replacement/reordering), plus routing guidance for surface_slug with a pointer to list_surfaces when multi-surface. Explicit when-to-use and when-to-use-something-else.

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

All Dock toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources