Skip to main content
Glama
nulab

Backlog MCP Server

get_resolutions

Retrieve a list of issue resolutions available in Backlog, enabling you to view or assign resolution statuses to issues.

Instructions

Returns list of issue resolutions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • Handler function for 'get_resolutions' tool. Calls backlog.getResolutions() to return the list of issue resolutions.
    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(),
      };
    };
  • Output schema for the 'get_resolutions' tool: an object with id (number) and name (string).
    export const ResolutionSchema = z.object({
      id: z.number(),
      name: z.string(),
    });
  • Input schema for 'get_resolutions' tool: empty object (no input parameters required).
    const getResolutionsSchema = buildToolSchema((_t) => ({}));
  • Import of getResolutionsTool into the central tools registry.
    import { getResolutionsTool } from './getResolutions.js';
  • Registration of getResolutionsTool within the 'issue' toolset in the allTools function.
    getResolutionsTool(backlog, helper),
Behavior2/5

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

No annotations provided, and description fails to disclose any behavioral traits (e.g., pagination, ordering, permissions, side effects). For a read tool, minimal disclosure of safe operation is missing.

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?

Extremely concise single sentence, front-loaded with purpose, no wasted words.

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 simple tool with one optional parameter and no output schema, the description is minimally adequate. However, it lacks differentiation from many sibling tools and does not clarify return format or behavior, leaving gaps.

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% with a helpful parameter description linking to list_organizations. The tool description adds no parameter information beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states verb 'Returns' and resource 'list of issue resolutions'. However, among many sibling tools that return lists (get_issues, get_categories, etc.), it does not distinguish what 'resolutions' specifically refers to.

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?

Implies use when needing issue resolutions, but no explicit guidance on when to use versus alternatives, no exclusions, and no mention of prerequisites like organization context.

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