Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_attachments

Read-only

Lists files attached to a Huly issue by issue identifier, enabling agents to inspect available attachments before referencing or processing them.

Instructions

List files attached to an issue

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": {
      "identifier": "<identifier>"
    },
    "name": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
identifierYesIssue id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.7/5.0
Behavior2/5

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

readOnlyHint=true already establishes this is a safe read, so the description carries a lower burden, yet it adds nothing beyond those annotations — no ordering, pagination, or result-size behavior. The only extra information is the implicit scoping to a single issue, which is already implied by the name.

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 brevity is efficient, though it borders on under-specification given the undocumented workspace parameter.

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 two-parameter list tool with no output schema, the agent still lacks guidance on the workspace parameter, whether results are paginated or complete, and what fields each attachment returns. The definition leaves too much for the caller to guess.

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 coverage is 50%: 'identifier' is documented as 'Issue id' in the schema, while 'workspace' is undocumented in both places. The description never mentions either parameter, so it does not compensate for the uncovered workspace parameter or clarify whether workspace is required for cross-workspace lookups.

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?

Specific verb 'List' plus resource 'files attached to an issue', which cleanly separates it from mutation siblings like attach_file. It stops short of naming the counterpart upload tool or scoping language (all attachments vs. filtered), so it is clear but not maximally differentiated.

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 indication of when to call this versus attach_file (the upload counterpart) or other list tools, and no mention of prerequisites such as needing the issue identifier. The agent must infer usage entirely from the verb.

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