Skip to main content
Glama
nulab

Backlog MCP Server

get_myself

Retrieve information about the currently authenticated Backlog user, including profile details and permissions.

Instructions

Returns information about the authenticated user

Input Schema

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

Implementation Reference

  • The handler function for the 'get_myself' tool. It calls backlog.getMyself() (from the backlog-js library) and returns the authenticated user's information.
    export const getMyselfTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getMyselfSchema>,
      (typeof UserSchema)['shape']
    > => {
      return {
        name: 'get_myself',
        description: t(
          'TOOL_GET_MYSELF_DESCRIPTION',
          'Returns information about the authenticated user'
        ),
        schema: z.object(getMyselfSchema(t)),
        outputSchema: UserSchema,
        importantFields: ['id', 'userId', 'name', 'roleType'],
        handler: async () => backlog.getMyself(),
      };
    };
  • UserSchema defines the output shape for get_myself tool: id, userId, name, roleType, lang, mailAddress, lastLoginTime.
    export const UserSchema = z.object({
      id: z.number(),
      userId: z.string(),
      name: z.string(),
      roleType: RoleTypeSchema,
      lang: LanguageSchema,
      mailAddress: z.string(),
      lastLoginTime: z.string(),
    });
  • Schema for get_myself — takes no parameters (empty object).
    const getMyselfSchema = buildToolSchema((_t) => ({}));
  • Registration of getMyselfTool in the 'space' toolset group.
    getMyselfTool(backlog, helper),
  • Import of getMyselfTool from './getMyself.js'.
    import { getMyselfTool } from './getMyself.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. It only states the basic function without revealing any behavioral traits like authentication assumptions, performance characteristics, or whether any data is mutated.

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 that directly conveys the purpose. No extraneous information; it is front-loaded and efficient.

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 getter with one optional parameter and no output schema, the description is minimally adequate. It does not specify the return format or field details, which could be helpful, but the simplicity of the tool makes this less critical.

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% and the parameter description in the schema is already clear ('Optional organization name. Use list_organizations to inspect available organizations.'). The tool description adds no further value beyond what the schema provides, earning a baseline 3.

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 uses a specific verb 'Returns' and identifies the resource as 'information about the authenticated user'. It clearly distinguishes from sibling tools like 'get_users' by focusing on the current authenticated user.

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 on when to use this tool versus alternatives such as 'get_users' or other user-related tools. The description does not mention contexts where this is preferred or when another tool might be better.

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