Skip to main content
Glama

assign_issue

Assign users to issues in AtomGit repositories to delegate tasks and track responsibility.

Instructions

Assign users to an issue in a AtomGit repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner
repoYesRepository name
issue_numberYesIssue number
assigneeYesList of assignees to be assigned

Implementation Reference

  • Handler for the 'assign_issue' tool: parses arguments using AssignIssueSchema, calls issues.setAssignee, and returns the JSON result.
    case "assign_issue": {
      const args = issues.AssignIssueSchema.parse(request.params.arguments);
      const { owner, repo, issue_number, assignee } = args;
    
      const result = await issues.setAssignee(owner, repo, issue_number, assignee);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema defining the input parameters for the assign_issue tool.
    export const AssignIssueSchema = z.object({
      owner: z.string().describe("Repository owner"),
      repo: z.string().describe("Repository name"),
      issue_number: z.number().describe("Issue number"),
      assignee: z.string().describe("List of assignees to be assigned"),
    });
  • index.ts:86-90 (registration)
    Tool registration in the ListTools response, specifying name, description, and input schema.
    {
      name: "assign_issue",
      description: "Assign users to an issue in a AtomGit repository",
      inputSchema: zodToJsonSchema(issues.AssignIssueSchema),
    },
  • Helper function that makes the POST request to the AtomGit API to assign a user to an issue.
    export async function setAssignee(
      owner: string,
      repo: string,
      issue_number: number,
      assignee: string
    ) {
      return atomGitRequest(
        `https://api.atomgit.com/repos/${encodeURIComponent(owner)}/${encodeURIComponent(repo)}/issues/${encodeURIComponent(issue_number)}/assignees`,
        {
          method: "POST",
          body: {
            assignee,
          },
        }
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('assign users') but doesn't describe what happens on success/failure, whether it overwrites existing assignees, if it requires specific permissions, or any rate limits. This leaves significant gaps for a mutation tool.

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 that communicates the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, what permissions are needed, or potential error conditions. The agent would need to guess about behavioral aspects beyond the basic action.

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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score for high schema coverage.

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?

The description clearly states the action ('assign users') and resource ('an issue in a AtomGit repository'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'list_issue_assignees' or 'check_if_user_is_assignable', which prevents a perfect score.

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. It doesn't mention prerequisites (like needing repository access), when assignment is appropriate, or how it differs from related tools like 'check_if_user_is_assignable' or 'list_issue_assignees'.

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/kaiyuanxiaobing/atomgit-mcp-server'

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