Skip to main content
Glama

Read DAT content (paginated)

get_dat_content
Read-only

Read a TouchDesigner DAT file with pagination, returning a sliced page of rows, total counts, and an optional stable header preview for large tables.

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 provide readOnlyHint and openWorldHint. Description adds significant behavioral context: the lossy split on tabs/newlines for cells, and the return structure (total row/col counts, header, sliced page, preview_rows, row_range). This goes beyond the annotations.

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?

Description is informative but slightly verbose. Front-loaded with core purpose. Could be tightened but still efficient.

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?

Given no output schema, the description explains return values clearly and includes the important caveat about lossy splitting. Covers pagination behavior and preview feature well.

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 coverage is 100%, so parameters are well-documented. Description adds minor context (e.g., preview_rows provides a 'stable head preview'), but most parameter meaning is already clear from schema.

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?

Clearly states 'Read a Text or Table DAT with pagination', specifying the verb (Read), resource (DAT content), and key feature (pagination). Distinguishes from sibling write tools edit_dat_content and set_dat_content.

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?

Explicitly mentions when to use pagination ('so a large table cannot flood context') and directs to write tools for writing. Does not explicitly state when not to use this tool, but context 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/Pantani/tdmcp'

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