Skip to main content
Glama

get_projects

Retrieve all projects from your Azure DevOps organization to view and manage development initiatives.

Instructions

Gets a list of all projects in the organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get_projects' tool, including its schema (empty input) and description, as part of the tools list returned by list_tools().
    types.Tool(
        name="get_projects",
        description="Gets a list of all projects in the organization.",
        inputSchema={
            "type": "object",
            "properties": {},
            "additionalProperties": False
        }
    ),
  • The handler logic within _execute_tool() for the 'get_projects' tool: fetches projects using the client and returns a dictionary with project names.
    elif name == "get_projects":
        projects = self.client.get_projects()
        return {"projects": [p.name for p in projects]}
  • Helper method in AzureDevOpsClient that delegates to the core Azure DevOps SDK client to retrieve the list of projects.
    def get_projects(self):
        return self.core_client.get_projects()
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 it 'Gets a list' which implies a read operation, but doesn't mention any behavioral traits like pagination, rate limits, permissions required, or what 'all projects' entails (e.g., archived vs. active). This leaves significant gaps for a tool with organizational scope.

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 function without any fluff. It's front-loaded with the core action and resource, making it immediately scannable and perfectly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with no parameters and no output schema, the description covers the basic purpose adequately. However, without annotations or output details, it lacks information about return format, error conditions, or organizational scope nuances, making it minimally viable but incomplete for confident use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately doesn't add parameter details, maintaining focus on the tool's purpose without redundancy. A baseline of 4 is appropriate for parameterless tools.

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 ('Gets') and resource ('list of all projects in the organization'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_repositories' or 'list_wiki_pages' that also list resources, so it doesn't reach the highest clarity level.

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, timing, or compare it to other listing tools in the sibling set, leaving the agent to infer usage context.

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

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