Skip to main content
Glama

get_org_repositories

Search and retrieve repositories from an AtomGit organization using organization path and optional search filters.

Instructions

Search for AtomGit org repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgPathYesSearch query org name
per_pageNoPage number for pagination (default: 1)
pageNoNumber of results per page (default: 10)
searchNoSearch query content

Implementation Reference

  • The primary handler function that constructs the AtomGit API URL for organization repositories, appends query parameters, fetches data using atomGitRequest, and returns the response.
    export async function getOrgRepositories(
      orgPath: string,
      per_page: number = 10,
      page: number = 1,
      search?: string
    ) {
      let url = `https://api.atomgit.com/orgs/${encodeURIComponent(orgPath)}/repos`;
    
      const params = new URLSearchParams();
      if (per_page) params.append('per_page', per_page.toString());
      if (page) params.append('page', page.toString());
      if (search) params.append('search', search);
    
      const queryString = params.toString();
      if (queryString) {
        url += `?${queryString}`;
      }
      const response = await atomGitRequest(url.toString());
      return response;
    }
  • Zod input schema defining parameters for the get_org_repositories tool: orgPath (required), per_page, page, and search (all optional).
    export const getOrgRepositoriesSchema = z.object({
      orgPath: z.string().describe("Search query org name"),
      per_page: z.number().optional().describe("Page number for pagination (default: 1)"),
      page: z.number().optional().describe("Number of results per page (default: 10)"),
      search: z.string().optional().describe("Search query content"),
    });
  • index.ts:116-120 (registration)
    MCP tool registration entry in the ListTools response, specifying the tool name, description, and input schema converted to JSON schema.
    {
      name: "get_org_repositories",
      description: "Search for AtomGit org repositories",
      inputSchema: zodToJsonSchema(repository.getOrgRepositoriesSchema),
    },
  • MCP CallTool dispatch handler that validates input arguments using the schema, invokes the core getOrgRepositories function, and returns the results formatted as MCP content.
    case "get_org_repositories": {
      const args = repository.getOrgRepositoriesSchema.parse(request.params.arguments);
      const results = await repository.getOrgRepositories(
        args.orgPath,
        args.per_page,
        args.page,
        args.search,
      );
      return {
        content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Search for' but doesn't clarify if this is a read-only operation, what permissions are needed, how results are returned, or any rate limits. This is inadequate for a tool with multiple parameters and no output schema.

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 no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 complexity (4 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain return values, error conditions, or behavioral traits, leaving significant gaps for the agent to operate effectively.

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 fully documents all 4 parameters. The description adds no additional meaning beyond implying a search functionality, which is already covered by the schema. Baseline 3 is appropriate as the schema handles parameter documentation.

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 ('Search for') and resource ('AtomGit org repositories'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get_user_repositories' or 'get_repository_labels' beyond the resource type, missing explicit 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, exclusions, or comparisons to sibling tools like 'get_user_repositories', leaving the agent to infer usage from context alone.

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