Skip to main content
Glama
xrmghost

MCP Azure DevOps Server

by xrmghost
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

set_project_context

Sets the project context for Azure DevOps commands to eliminate repetitive project parameter entry in subsequent operations.

Instructions

Sets the project context for subsequent commands to avoid repeating project parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project to set as context.

Implementation Reference

  • mcp_azure_devops/azure_devops_client.py:60-62 (handler)
    The main handler function in AzureDevOpsClient that sets the project_context attribute and returns a confirmation message.
    def set_project_context(self, project):
    self.project_context = project
    return {"message": f"Project context set to '{project}'."}
  • mcp_azure_devops/server.py:524-534 (schema)
    The JSON schema defining the input parameters for the set_project_context tool, requiring a 'project' string.
    inputSchema={
    "type": "object",
    "properties": {
        "project": {
            "type": "string", 
            "description": "The name or ID of the project to set as context."
        },
    },
    "required": ["project"],
    "additionalProperties": False
}
  • mcp_azure_devops/server.py:521-535 (registration)
    The tool registration in the server's tools list, including name, description, and schema.
    types.Tool(
    name="set_project_context",
    description="Sets the project context for subsequent commands to avoid repeating project parameter.",
    inputSchema={
        "type": "object",
        "properties": {
            "project": {
                "type": "string", 
                "description": "The name or ID of the project to set as context."
            },
        },
        "required": ["project"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:1057-1058 (handler)
    The server-side dispatch handler that routes the tool call to the client's set_project_context method.
    elif name == "set_project_context":
    return self.client.set_project_context(**arguments)

Tool Definition Quality

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool sets context for subsequent commands, implying stateful behavior, but doesn't disclose how long the context persists, whether it's session-specific, what happens on errors, or if it affects all sibling tools. For a state-changing tool with zero annotation coverage, this is a significant gap.

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 front-loads the purpose ('Sets the project context') and explains the benefit ('to avoid repeating project parameter'). There is zero waste, and every word earns its place.

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?

Given one parameter with full schema coverage and no output schema, the description adequately covers the basic purpose. However, as a state-setting tool with no annotations, it lacks details on persistence, scope, error handling, and how it integrates with other tools, making it minimally viable but with clear gaps.

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 the parameter 'project' fully documented in the schema as 'The name or ID of the project to set as context.' The description doesn't add any meaning beyond this, such as format examples or validation rules, so it 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 ('Sets') and resource ('project context'), explaining it avoids repeating project parameters. It distinguishes from 'clear_project_context' by being the setter rather than clearer, but doesn't explicitly differentiate from other project-related tools like 'get_projects'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you want to avoid repeating project parameters in subsequent commands, providing some context. However, it doesn't explicitly state when not to use it (e.g., for one-off commands) or mention alternatives like directly specifying project in each command, and no guidance on prerequisites or interactions with other tools.

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