Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Read Attachment

read_attachment
Read-only

Read a slice of any file in the user's attachment library, by id.

Use this when the attachment summary doesn't contain enough data to answer. For spreadsheets, paginate with row_start/row_end (default window = 500 rows). For PDFs/PPTX and text files, use page_start/page_end (1-indexed, inclusive; default window = 10 pages). When the result has truncated=True, advance page_start to read on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetNofor multi-sheet xlsx, the sheet name (default: first sheet)
columnsNolist of column names to keep (default: all)
row_endNozero-indexed, exclusive (default: row_start + 500)
page_endNo1-indexed, inclusive (PDFs/PPTX/text files)
row_startNozero-indexed, inclusive
page_startNo1-indexed, inclusive (PDFs/PPTX/text files)
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
attachment_idYesa file id from list_attachments or an [Attachment: id=N] summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds genuine behavioral context: per-format pagination windows (500 rows, 10 pages), 1-indexed inclusive semantics, and the truncated=True continuation protocol. It doesn't discuss size limits or failure modes, keeping it from a 5.

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?

Front-loaded with the core purpose, then a compact usage trigger, then the format-specific pagination rules. Every sentence carries operational information with 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 an 8-param reader with no output schema, the description covers the usage trigger, pagination mechanics, and the truncated=True return signal. It omits mention of sheet/columns/on_behalf_of behavior, though those are documented in the schema.

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 real semantics beyond the schema: the default row window of 500, the default page window of 10, and the rule for advancing page_start when truncated. The non-pagination params (sheet, columns, on_behalf_of) are left to the 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?

Specific verb+resource+scope: 'Read a slice of any file in the user's attachment library, by id.' It clearly distinguishes itself from list_attachments (which enumerates) and the email attachment readers by operating on the attachment library by id.

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?

Gives a clear trigger condition: 'Use this when the attachment summary doesn't contain enough data to answer,' which tells the agent when to escalate from summary to full read. It does not explicitly name alternative sibling tools, so it stops short of a 5.

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

All Sliq 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