Skip to main content
Glama
nulab

Backlog MCP Server

get_resolutions

Retrieve available issue resolution options from Backlog to categorize and track project task completion status.

Instructions

Returns list of issue resolutions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getResolutionsTool function defines and returns the tool configuration, including the handler that executes the core logic by calling backlog.getResolutions().
    export const getResolutionsTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getResolutionsSchema>,
      (typeof ResolutionSchema)['shape']
    > => {
      return {
        name: 'get_resolutions',
        description: t(
          'TOOL_GET_RESOLUTIONS_DESCRIPTION',
          'Returns list of issue resolutions'
        ),
        schema: z.object(getResolutionsSchema(t)),
        outputSchema: ResolutionSchema,
        handler: async () => backlog.getResolutions(),
      };
    };
  • Input schema for the get_resolutions tool, defined as an empty object since the tool takes no parameters.
    const getResolutionsSchema = buildToolSchema((_t) => ({}));
  • The getResolutionsTool is registered/added to the 'issue' toolset group in the allTools function.
    getResolutionsTool(backlog, helper),
  • Import of the getResolutionsTool function.
    import { getResolutionsTool } from './getResolutions.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Returns list' implies a read-only operation, but it doesn't specify whether this is a complete list, paginated, filtered, or cached. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered about performance, data freshness, or access requirements.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose ('Returns list of issue resolutions') and contains no redundant information. This is an excellent example of appropriate conciseness for a simple tool.

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?

For a zero-parameter tool with no output schema, the description provides the minimum viable information about what the tool does. However, without annotations or output schema, it doesn't address important contextual questions like what format the list returns in, whether it's paginated, or what authentication might be required. The description is adequate but leaves clear gaps in understanding the tool's behavior.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of parameters. The description appropriately doesn't add parameter information beyond what the schema provides, maintaining focus on the tool's purpose rather than unnecessary parameter details.

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

Purpose3/5

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

The description 'Returns list of issue resolutions' clearly states the verb ('returns') and resource ('issue resolutions'), making the basic purpose understandable. However, it doesn't distinguish this tool from similar sibling tools like 'get_issue_types' or 'get_priorities' that also return lists of metadata, leaving room for confusion about when to use this specific tool.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools available (like 'get_issues' for actual issues or 'get_issue_types' for issue types), there's no indication whether this should be used for reference data, filtering options, or other contexts. The agent receives no usage context beyond the basic purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nulab/backlog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server