Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official
by openl-tablets
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Get Table Structure & Data

openl_get_table
Read-onlyIdempotent

Get a table's raw 2D cell matrix to read authoritative workbook content; slice large tables by rows and optionally include Excel styles.

Instructions

Get a table as its authoritative RawSource 2D cell matrix. Typed/parsed table views are intentionally unsupported because they are incomplete and cannot safely round-trip workbook content. startRow/maxRows read a large table in row slices (a windowed response carries totalRows), and styles=true adds each cell's Excel style. A window cannot replace the whole table: openl_update_table rejects totalRows and independently refuses a source with fewer rows than the live table, so removing the marker cannot erase omitted rows. For a large table whose complete response becomes a preview, use the narrow raw table action tools instead. A table id changes when an edit relocates the table; stale ids produced by this server are resolved automatically, otherwise refresh ids with openl_list_tables().

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stylesNoIf true, each raw cell carries its Excel style (background/font colour, bold/italic/underline, alignment, indent, borders).
maxRowsNoMaximum number of source rows, counted from startRow; omit to read to the end. A windowed response carries totalRows.
tableIdYesTable identifier - unique ID assigned by OpenL Studio (e.g., 'calculatePremium_1234'). VOLATILE: derived from the table's location, so it changes when an edit relocates the table (it had no room to grow in place) — use the 'tableId' returned by the latest openl_update_table/openl_append_table response, or refresh via openl_list_tables().
startRowNoZero-based index of the first source row; omit to start at the top. Combine with maxRows to read a large table in slices.
projectIdYesProject ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.
response_formatNoResponse format: 'json' for structured, round-trippable data (default), 'markdown' for human-readable output, 'markdown_concise' for a brief summary (1-2 paragraphs), or 'markdown_detailed' for full details with contextjson

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv1.2.0
    • addedInput schema / properties / maxRows
      Added value: +{
+  "description": "Maximum number of source rows, counted from startRow; omit to read to the end. A windowed response carries totalRows.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / raw
      Removed value: -{
-  "description": "If true, returns the raw table view as a 2D matrix of cells without any parsing or structure interpretation. Useful for reading tables of unknown or custom types, preserving exact cell positioning and merge regions.",
-  "type": "boolean"
-}
    • changedInput schema / properties / response_format / default
      Previous value: -"markdown"New value: +"json"
    • changedInput schema / properties / response_format / description
      Previous value: -"Response format: 'json' for structured data, 'markdown' for human-readable (default), 'markdown_concise' for brief summary (1-2 paragraphs), 'markdown_detailed' for full details with context"New value: +"Response format: 'json' for structured, round-trippable data (default), 'markdown' for human-readable output, 'markdown_concise' for a brief summary (1-2 paragraphs), or 'markdown_detailed' for full details with context"
    • addedInput schema / properties / startRow
      Added value: +{
+  "description": "Zero-based index of the first source row; omit to start at the top. Combine with maxRows to read a large table in slices.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / styles
      Added value: +{
+  "description": "If true, each raw cell carries its Excel style (background/font colour, bold/italic/underline, alignment, indent, borders).",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.1.0
    • changedInput schema / properties / tableId / description
      Previous value: -"Table identifier - unique ID assigned by OpenL Studio when table is created (e.g., 'calculatePremium_1234')"New value: +"Table identifier - unique ID assigned by OpenL Studio (e.g., 'calculatePremium_1234'). VOLATILE: derived from the table's location, so it changes when an edit relocates the table (it had no room to grow in place) — use the 'tableId' returned by the latest openl_update_table/openl_append_table response, or refresh via openl_list_tables()."
  3. First observedv0.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Even with readOnly/idempotent/openWorld annotations, the description adds substantial behavioral detail: RawSource is authoritative, typed/parsed views are intentionally unsupported for round-trip safety, windowed responses carry totalRows, and stale table IDs are auto-resolved. It also explains why a window cannot erase omitted rows, which is valuable safety context.

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?

The description is long but front-loaded with the core purpose and every sentence earns its place: caveats about typed views, slicing, window safety, alternative tools, and ID volatility. It is dense rather than bloated, though a slightly more compact treatment of the window-safety warning would improve it.

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 6-parameter read tool with no output schema, the description covers return mode, row-slicing behavior, style enrichment, window limitations, and ID handling. It could say a bit more about the shape of the returned RawSource cell matrix, but the guidance is sufficient for correct invocation.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining how startRow/maxRows combine to slice a table, what styles=true produces, and why tableId is volatile. The projectId and response_format parameters remain covered by the schema alone.

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?

The opening sentence states a specific action and resource: 'Get a table as its authoritative RawSource 2D cell matrix.' It also distinguishes itself from typed/parsed views and from the narrow raw table tools, so an agent can tell what mode this getter operates in.

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

Usage Guidelines4/5

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

The description gives clear usage context: use slicing with startRow/maxRows for large tables, and choose the narrow raw table action tools when a complete response would become a preview. It is slightly vague because 'narrow raw table action tools' is not explicitly enumerated, but the routing intent is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openl-tablets/openl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server