Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

get_project

Retrieve project details from Azure DevOps by specifying project and organization identifiers to access configuration, settings, and metadata.

Instructions

Get details of a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe ID or name of the project (Default: MyProject)
organizationIdNoThe ID or name of the organization (Default: mycompany)

Implementation Reference

  • The getProject function implements the core logic of the 'get_project' tool by fetching the project details from Azure DevOps Core API using the project ID or name.
    export async function getProject(
      connection: WebApi,
      projectId: string,
    ): Promise<TeamProject> {
      try {
        const coreApi = await connection.getCoreApi();
        const project = await coreApi.getProject(projectId);
    
        if (!project) {
          throw new AzureDevOpsResourceNotFoundError(
            `Project '${projectId}' not found`,
          );
        }
    
        return project;
      } catch (error) {
        if (error instanceof AzureDevOpsError) {
          throw error;
        }
        throw new Error(
          `Failed to get project: ${error instanceof Error ? error.message : String(error)}`,
        );
      }
    }
  • The switch case handler in handleProjectsRequest that parses arguments, calls getProject, and formats the response for the 'get_project' tool invocation.
    case 'get_project': {
      const args = GetProjectSchema.parse(request.params.arguments);
      const result = await getProject(
        connection,
        args.projectId ?? defaultProject,
      );
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema definition for validating the input parameters of the 'get_project' tool.
    export const GetProjectSchema = z.object({
      projectId: z
        .string()
        .optional()
        .describe(`The ID or name of the project (Default: ${defaultProject})`),
      organizationId: z
        .string()
        .optional()
        .describe(`The ID or name of the organization (Default: ${defaultOrg})`),
    });
  • Registration of the 'get_project' tool in the projectsTools array, defining its name, description, and input schema.
      name: 'get_project',
      description: 'Get details of a specific project',
      inputSchema: zodToJsonSchema(GetProjectSchema),
    },
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 tool retrieves details but doesn't mention permissions needed, rate limits, error conditions, or what 'details' includes (e.g., fields returned). This is inadequate for a read operation with zero annotation coverage.

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 ('Get details'), 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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'details' entails, potential authentication needs, or error handling. For a tool with siblings like 'get_project_details', more context is needed to differentiate 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%, so parameters are fully documented in the schema. The description adds no additional meaning about 'projectId' or 'organizationId' beyond what the schema provides, meeting the baseline for high 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 verb 'Get' and resource 'details of a specific project', making the purpose unambiguous. However, it doesn't distinguish this tool from sibling 'get_project_details', which appears to serve a similar function, preventing 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 like 'get_project_details' or 'list_projects'. It lacks context about prerequisites, exclusions, or comparison with sibling tools, leaving the agent with minimal usage direction.

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/Tiberriver256/mcp-server-azure-devops'

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