Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

List Attachments

list_attachments
Read-only

List the files in the user's attachment library — id, filename, type, size.

Defaults to global company-context files plus files belonging to the current agent or chat. Set all_agents=True to list the user's whole library across agents. Use a returned id with read_attachment or attach_to_outreach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
all_agentsNolist the whole library instead of just the current agent's 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.

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. Changed2 schema fields changed
    • addedInput schema / properties / all_agents
      Added value: +{
+  "default": false,
+  "description": "list the whole library instead of just the current agent's files.",
+  "type": "boolean"
+}
    • removedInput schema / properties / all_tasks
      Removed value: -{
-  "default": false,
-  "description": "list the whole library instead of just the current task's files.",
-  "type": "boolean"
-}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the extra burden and discharges it partly: it discloses the default result scope (company-context + current agent/chat) and what the all_agents flag changes. It does not mention anything about the on_behalf_of acting context, pagination, or result limits.

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?

Three tight sentences: what it lists first, the default scope second, the widening flag third, and the follow-up tools last. No filler and nothing important buried.

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?

There is no output schema, but the description names the returned fields, the default scope, the flag that changes it, and the downstream consumers, which is everything an agent needs to call and use this read-only list tool correctly.

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 100%, so the baseline is 3. The description goes slightly beyond the schema's own wording by spelling out what the default scope actually contains (global company-context files plus current agent/chat files), which the all_agents schema description does not state. on_behalf_of is left entirely 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?

States a specific verb+resource ('List the files in the user's attachment library') and even enumerates the returned fields (id, filename, type, size). It also names sibling tools (read_attachment, attach_to_outreach) that consume the output, so an agent can distinguish this listing tool from the attachment-reading tools without opening a schema.

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 an explicit default scope (global company-context files plus files belonging to the current agent or chat) and an explicit conditional for widening it (all_agents=True). It also routes the agent forward ('use a returned id with read_attachment or attach_to_outreach'). It stops short of stating when this tool should NOT be used versus the other attachment-fetching siblings.

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