Skip to main content
Glama

doer_upload_attachment

Upload files from local paths or base64 data to attach them to a Doer todo list by providing the list ID and file details.

Instructions

Upload one or more files to attach to a todo list in Doer (accepts local file paths or base64 data)

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>",
      "files": "<files>"
    },
    "name": "doer_upload_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesFiles to attach (path on disk or base64 content)
todo_list_idYesUnique identifier of the todo list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that one or more files are accepted and that paths or base64 are supported; it says nothing about upload limits, whether existing attachments are preserved, permission/auth requirements, or what the call returns on success or failure.

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?

A single, front-loaded sentence with no filler; the core action and target resource come first and the input modality follows. It is not padded, though the parenthetical adds little beyond the schema.

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

Completeness3/5

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

With no annotations and no output schema, the description should say more about behavior for a mutating upload tool — side effects, limits, and error conditions are absent. What it does cover (purpose and accepted input forms) is adequate for a two-parameter tool whose schema is fully documented.

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%, so the schema already documents todo_list_id, files, path, filename, content_type, and content_base64 thoroughly. The description's parenthetical about local paths and base64 merely restates the schema rather than adding format, constraint, or precedence rules (e.g. what wins when both path and content_base64 are given).

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 states a specific verb and resource: upload files to attach to a todo list in Doer. It clearly distinguishes itself from siblings such as doer_list_attachments or doer_delete_attachment by naming the attach/upload action, though it never explicitly names those siblings.

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

Usage Guidelines3/5

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

Usage is implied by "attach to a todo list" — an agent can infer this is the tool for adding attachments. However, there is no explicit when-to-use guidance, no mention of prerequisites (e.g. the todo list must exist), and no routing to alternatives like doer_list_attachments for inspection.

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