Skip to main content
Glama

doer_list_attachments

Lists file attachments for a Doer todo list using its unique ID, so you can review files linked to that list.

Instructions

List file attachments associated with a todo list in Doer

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "todo_list_id": "<todo_list_id>"
    },
    "name": "doer_list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_list_idYesUnique identifier of the todo list whose attachments to list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read operation. It says nothing about pagination, ordering, what happens when the list has no attachments, or whether attachment contents/URLs are included in the response.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the gaps noted in other dimensions rather than being a structural problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required integer parameter), but with no output schema and no annotations, the description should say at least something about the shape of returned attachments. As written, an agent knows what to pass but not what it will get back or how failures present.

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 description coverage is 100% and the single parameter todo_list_id is fully documented, so the baseline is 3. The description adds no meaning beyond the schema (no notes on ID validity or how to obtain one), so it does not exceed that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('List') plus a specific resource ('file attachments') scoped to a todo list in Doer, which cleanly separates it from doer_upload_attachment and doer_delete_attachment. It stops short of naming a sibling or contrasting behavior, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives such as doer_get_todo_list (which may or may not surface the same data) or how it relates to the upload/delete attachment tools. The intended use is only inferable from the tool name and the phrase 'associated with a todo list'.

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