Skip to main content
Glama
mmruesch12
by mmruesch12

get_project

Retrieve specific details of an Azure DevOps project by using its ID or name. This tool simplifies project information access for streamlined management and oversight.

Instructions

Get details of a specific Azure DevOps project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID (GUID) of the project
nameNoName of the project

Implementation Reference

  • The main handler function for the 'get_project' tool. It parses input parameters using getProjectSchema, fetches the project details via coreClient.getProject using either ID or name, and returns formatted JSON content or an error response.
    export async function getProject(rawParams: any) {
      // Parse arguments
      const params = getProjectSchema.parse({
        id: rawParams.id,
        name: rawParams.name,
      });
    
      console.error("[API] Getting project details:", params);
    
      try {
        // Get the Core API client
        const coreClient = await getCoreClient();
    
        // Check if we have an identifier
        const projectIdentifier = params.id || params.name;
        if (!projectIdentifier) {
          throw new Error("Either project ID or name must be provided");
        }
    
        // Call the API to get project details
        const project = await coreClient.getProject(projectIdentifier, true);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(project, null, 2),
            },
          ],
        };
      } catch (error) {
        logError("Error getting project details", error);
        return {
          content: [
            {
              type: "text",
              text: `Error getting project details: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema definition for 'get_project' input validation (requires either project ID or name) and the inferred TypeScript type GetProjectParams.
     */
    export const getProjectSchema = z
      .object({
        id: z.string().optional(),
        name: z.string().optional(),
      })
      .refine((data) => data.id || data.name, {
        message: "Either id or name must be provided",
      });
    
    export type GetProjectParams = z.infer<typeof getProjectSchema>;
  • Tool registration metadata within the projectTools array, defining name, description, and input schema for 'get_project'.
    {
      name: "get_project",
      description: "Get details of a specific Azure DevOps project",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "ID (GUID) of the project",
          },
          name: {
            type: "string",
            description: "Name of the project",
          },
        },
        required: [],
      },
    },
  • src/index.ts:99-100 (registration)
    Dispatcher in the main CallToolRequest handler that routes 'get_project' calls to the getProject function.
    case "get_project":
      return await getProject(request.params.arguments || {});
  • src/index.ts:60-60 (registration)
    Inclusion of projectTools (containing 'get_project') in the ListToolsRequest response.
    ...projectTools,
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 the tool retrieves details but doesn't describe the return format (e.g., JSON structure), error handling (e.g., if project not found), authentication requirements, or rate limits. This leaves significant gaps for an agent to understand how to interact with it effectively.

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, direct sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded with the key action and resource, making it easy to parse. There is no wasted verbiage or redundancy.

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 that likely returns structured data. It doesn't explain what 'details' include (e.g., project metadata, settings), how results are formatted, or potential side effects. For a read operation with two parameters, more context is needed to ensure reliable agent use.

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?

The input schema has 100% description coverage, documenting both parameters ('id' and 'name') with their types and purposes. The description adds no additional parameter information beyond what the schema provides, such as usage examples or constraints (e.g., only one parameter needed). This meets the baseline 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 ('Get details') and resource ('specific Azure DevOps project'), making the purpose immediately understandable. It distinguishes from siblings like 'list_projects' by focusing on a single project rather than listing multiple. However, it doesn't specify what details are included, 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?

No explicit guidance is provided on when to use this tool versus alternatives. While it implies usage for retrieving details of a known project, it doesn't mention prerequisites (e.g., needing project ID or name), compare it to 'list_projects' for discovery, or specify when not to use it (e.g., for bulk operations).

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

Related 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/mmruesch12/azdo-mcp'

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