Skip to main content
Glama

get_ticket_attachment

Fetch a ticket attachment's content by UUID. Returns text/CSV inline, images as viewable blocks, and writes other file types or large files to disk via save_to.

Instructions

Fetch one attachment's CONTENT, having found its uuid with list_ticket_attachments. What comes back depends on what the file is, because a tool result is text and most files are not: a text or CSV attachment is returned inline as text; an image is returned as an image block, which is the only form the model can actually look at; anything else — a PDF, a spreadsheet, a document — cannot cross this boundary as text at all, and needs save_to. Pass save_to for any file you want on disk, and for anything large: it writes the bytes to that path on the machine THIS SERVER runs on (normally the same machine as the agent, since the client starts it as a subprocess) and returns the path and size instead of the content. Files over 4 MB always need save_to, whatever their type, because an inline result that size costs more context than the answer is worth. Missing, still uploading, deleted, or on a ticket you cannot open are all the same 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
save_toNoAbsolute path to write the file to, on the machine running this server. Parent directories are created. An existing file is overwritten
task_uuidYesThe ticket's uuid, from list_tickets, get_board or search
attachment_uuidYes
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses content-type-dependent returns, server-side file writing, path/size return instead of content, the 4 MB context-cost rule, and the unified 404 for missing/uploading/deleted/permission-denied attachments. This is excellent disclosure beyond anything structural annotations could provide.

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 action and every clause provides necessary operational detail about file-type behavior and save_to. It is dense rather than wasteful; a bit of tightening would make it more concise, but the current length is justified by the tool's complexity.

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?

For a complex tool with no annotations and no output schema, the description is complete: it covers invocation prerequisite, return behavior for all file categories, save_to usage and location, size thresholds, and error semantics. An agent has enough information to invoke the tool correctly and predict outcomes.

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 description coverage is 67% with attachment_uuid lacking a description. The tool description compensates by stating the attachment_uuid comes from list_ticket_attachments and by adding deep semantics for save_to (server machine, path/size return, overwrite behavior). It adds clear meaning beyond the schema's bare field 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 opens with 'Fetch one attachment's CONTENT' and clarifies that the result depends on the file type, tying the attachment uuid to list_ticket_attachments. This clearly distinguishes the tool from sibling list/upload/delete attachment tools and states its exact resource and action.

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?

It explicitly instructs users to first find the uuid via list_ticket_attachments and gives conditional guidance: text/CSV inline, image blocks, and save_to for binary/large files with a 4 MB threshold. It lacks explicit 'when not to use' exclusions, but the context for using the tool and its save_to parameter is strong.

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/Developyn/laver-mcp'

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