Skip to main content
Glama

Read DAT content (paginated)

get_dat_content
Read-only

Read Text or Table DAT files with pagination to prevent context overflow. Returns row/column counts, header, a page slice, and optional head preview for large datasets.

Instructions

Read a Text or Table DAT with pagination so a large table cannot flood context. Returns total row/col counts, a header (table DATs), a sliced page (offset/limit), an optional stable head preview (preview_rows), and a row_range only on a partial read. Table DATs are split on tabs/newlines client-side — that split is lossy if a cell embeds a literal tab or newline (probe live before relying on it). Use edit_dat_content/set_dat_content to write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows/lines to return. Capped so a large table never floods context.
offsetNoFirst data-row index to return (0-based). For a table DAT it indexes data rows (after the header when include_header is true); for a non-table Text DAT it indexes lines.
dat_pathYesAbsolute path to the Text or Table DAT to read (e.g. '/project1/table1').
preview_rowsNoIf > 0, ALSO return the first N rows regardless of offset — a stable head preview alongside a deep page. 0 disables the separate preview.
include_headerNoFor table DATs, treat row 0 as a header: return it in `header` and make offset/limit index the data rows after it. Set false to treat every row as data.
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds significant context: return structure (total counts, header, sliced page, preview, row_range), the lossy split caveat for cells with embedded tabs/newlines, and the advisory to probe live data. This goes well beyond the annotation baseline, though it doesn't cover error handling or invalid paths.

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?

Two sentences, densely packed with essential information. The first sentence front-loads the purpose and return values; the second provides a critical caveat and points to write tools. Every word earns its place.

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?

With no output schema, the description fully explains the return values (total row/col counts, header, sliced page, preview, row_range) and covers the lossy split limitation. It also addresses pagination intent and the presence of sibling write tools, making it complete for a read tool of this complexity.

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% with rich descriptions. The description adds extra meaning by explaining how offset/limit interact with the header, how preview_rows provides a stable head preview, and when row_range appears. This clarifies parameter behavior beyond the schema's individual definitions.

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 description clearly states this tool reads a Text or Table DAT with pagination, distinguishing it from sibling tools like edit_dat_content and set_dat_content. The verb 'Read' and resource 'DAT' are specific, and the pagination purpose is explicit.

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?

It explicitly names edit_dat_content/set_dat_content as the tools to use for writing, providing a clear alternative. It also explains when pagination is useful (to avoid flooding context) and warns about probing live data before relying on the table split.

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/lucasmaher-hash/touch-designer-mcp'

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