Skip to main content
Glama
Sign In
productive-mcp-rb2

productive-mcp-rb2

by rubenlangeweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_attachments

list_attachments
Read-onlyIdempotent

List file attachments on a task or comment in Productive.io, returning filenames, types, sizes, and download URLs.

Instructions

List file attachments on a task or comment in Productive.io. Returns filenames, types, sizes, and download URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoThe ID of the task to list attachments for
comment_idNoThe ID of the comment to list attachments for
limitNoNumber of attachments to return (1-200, default 30)

Output Schema

NameRequiredDescriptionDefault
attachmentsYes
returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-alpha.7

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the tool as readOnly and idempotent. The description adds that it returns specific fields. No mention of pagination or rate limits, but the overall behavior is clear and consistent with annotations.

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?

The description is a single, direct sentence that conveys all necessary information without unnecessary words. It is front-loaded with the main action.

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?

The description covers the purpose and return values. With an output schema present (indicated true), it does not need to detail return fields. Could mention pagination behavior, but the limit parameter is documented in the schema.

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 coverage is 100%, so the description does not need to add parameter details. The description mentions 'on a task or comment' which aligns with task_id and comment_id parameters but does not add new semantics beyond 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?

The description clearly states the action ('List'), the resource ('file attachments on a task or comment'), and the data returned ('filenames, types, sizes, and download URLs'). It distinguishes from sibling tools because no other tool lists attachments.

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?

The description implies usage for retrieving attachments from a specific task or comment, but does not explicitly state when to use it vs alternatives or provide exclusion criteria. No guidance on when not to use.

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

Deploy Server

Other Tools