Skip to main content
Glama

get_repository_labels

Retrieve all labels from an AtomGit repository to organize issues and pull requests. Specify the repository owner and name to access label data.

Instructions

Get all labels in a repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner, typically referred to as 'username'. Case-insensitive.
repoYesRepository name. Case-insensitive.

Implementation Reference

  • Core handler function that makes the AtomGit API request to fetch all labels for the specified repository.
    export async function getLabels(
      owner: string,
      repo: string
    ) {
      return atomGitRequest(
        `https://api.atomgit.com/repos/${encodeURIComponent(owner)}/${encodeURIComponent(repo)}/labels`,
        {
          method: "GET",
        }
      );
    }
  • Zod schema defining the input parameters for the get_repository_labels tool: owner and repo.
    export const GetLabelsSchema = z.object({
      owner: z.string().describe("Repository owner, typically referred to as 'username'. Case-insensitive."),
      repo: z.string().describe("Repository name. Case-insensitive."),
    });
  • index.ts:177-181 (registration)
    Registration of the get_repository_labels tool in the MCP server's tool list, including schema reference.
    {
      name: "get_repository_labels",
      description: "Get all labels in a repository",
      inputSchema: zodToJsonSchema(label.GetLabelsSchema),
    },
  • Dispatcher case in the CallToolRequestHandler that parses arguments, calls the core getLabels function, and formats the response.
    case "get_repository_labels": {
      const args = label.GetLabelsSchema.parse(request.params.arguments);
      const { owner, repo } = args;
    
      const result = await label.getLabels(owner, repo);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'Get all labels' but doesn't describe what 'all' entails (e.g., pagination, rate limits, authentication needs, or return format). For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly. Every word earns its place by conveying 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?

Given the lack of annotations and output schema, the description is incomplete for a tool with behavioral complexity. It doesn't address key aspects like return format (e.g., list of label objects), pagination, error handling, or authentication requirements. For a read operation that might involve multiple items, more context is needed to ensure proper usage.

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%, with both parameters ('owner' and 'repo') well-documented in the schema. The description adds no additional parameter information beyond what the schema provides, such as examples or edge cases. Given the high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to.

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 verb 'Get' and resource 'all labels in a repository', making the purpose immediately understandable. It distinguishes from siblings like 'get_issue_labels' (which is issue-specific) and 'get_label_by_name' (which retrieves a single label), though it doesn't explicitly mention these distinctions. The description is specific but could be more precise about sibling differentiation.

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 when to choose this over 'get_issue_labels' (for issue-specific labels) or 'get_label_by_name' (for a single label), nor does it specify prerequisites like repository access. Usage is implied by the name but not explicitly stated.

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