Skip to main content
Glama
Sign In
ado-workflows-mcp

ado-workflows-mcp

by grimlor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

establish_pr_context

Create reusable PR context by parsing a full Azure DevOps PR URL or resolving a numeric PR ID using cached repository context.

Instructions

Create reusable PR context from a URL or numeric ID.

Parses a full PR URL or resolves a numeric PR ID using cached repository context.

Args: pr_url_or_id: A full Azure DevOps PR URL or a numeric PR ID. working_directory: Optional path for context resolution when using a numeric ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pr_url_or_id": "<pr_url_or_id>"
    },
    "name": "establish_pr_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pr_url_or_idYes
working_directoryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the core behavior—creating context from input—but does not disclose side effects, permissions, or whether it modifies state. The description is transparent about the main action but lacks depth.

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 concise: two sentences followed by parameter explanations. It is front-loaded with the main purpose and avoids redundancy. Every sentence adds value, and the structure is clear.

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

Completeness4/5

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

Given the tool has two parameters, no annotations, and an output schema exists, the description is reasonably complete. It explains both parameters and the general behavior. The output schema covers return values, so the description does not need to detail them. Minor gap: vague on what 'reusable context' means in practice.

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?

With 0% schema description coverage, the description adds significant meaning: it clarifies that 'pr_url_or_id' can be a full URL or numeric ID, and explains 'working_directory' as an optional path for context resolution. This goes well beyond the schema's basic type information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create reusable PR context from a URL or numeric ID' and explains it parses PR URLs or resolves numeric IDs using cached context. The verb 'create' and resource 'PR context' are specific, and the tool is clearly differentiated from siblings like 'establish_work_item_context'.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for setting up context before other PR operations, but there are no when-not conditions or mentions of alternatives. The guidance is adequate but minimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools