Skip to main content
Glama
Sign In
HacknPlan MCP

HacknPlan MCP

by jompereira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_work_item_attachments

Retrieve all file attachments for a specific work item in a HacknPlan project by supplying project and work item IDs.

Instructions

List all attachments on a work item

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": {
      "projectId": "<projectId>",
      "workItemId": "<workItemId>"
    },
    "name": "list_work_item_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
workItemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It does not mention whether results are paginated, if authorization is required, or any side effects. The minimal description leaves significant gaps.

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 sentence with no unnecessary words. It is efficient and to the point.

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?

For a list tool with 2 parameters and no output schema, the description is incomplete. It omits details like return format, pagination, or any filtering capabilities. The agent may need additional context to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should add meaning. While 'projectId' and 'workItemId' are self-explanatory, no further details are provided, such as where to obtain these IDs or any constraints.

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 verb 'List', the resource 'attachments', and the context 'on a work item'. It is specific and helps distinguish from siblings like delete_work_item_attachment or list_design_element_attachments.

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?

No guidance is provided on when to use this tool versus alternatives such as get_work_item_attachment for a single attachment or list_design_element_attachments. No prerequisites or exclusion criteria are mentioned.

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