Android-MCP

Overview Schema Source Related Servers Discussions Admin

Report-Bug-To-Azure-Direct

Create a structured bug report in Azure DevOps by supplying title, steps to reproduce, expected and actual results, priority, and severity for efficient issue tracking.

Instructions

[EXPERIMENTAL] Report a bug to Azure DevOps - direct execution (may hang)

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": {
      "title": "<title>",
      "steps_to_reproduce": "<steps_to_reproduce>",
      "expected_result": "<expected_result>",
      "actual_result": "<actual_result>"
    },
    "name": "Report-Bug-To-Azure-Direct"
  }
}

Input Schema

Name	Required	Default
`title`	Yes
`project`	No
`priority`	No
`severity`	No	3 - Medium
`description`	No
`environment`	No
`actual_result`	Yes
`expected_result`	Yes
`parent_user_story`	No
`steps_to_reproduce`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose two meaningful risks: the tool is experimental and it may hang. However, it does not mention authentication requirements, whether a work item is actually created, failure behavior, or side effects beyond reporting a bug. It adds some value but still leaves significant behavioral unknowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the experimental warning and hang risk, which are useful. However, for a tool with 10 parameters and no schema coverage, the single-sentence description is more under-specified than appropriately concise. It contains no redundant text, but it does not earn its place as a complete guide.

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?

The tool is moderately complex with 10 parameters, no output schema, and no annotations, yet the description only provides a basic purpose and a hang warning. It omits when to use the direct variant, expected return behavior, error outcomes, and any setup requirements. The description is not complete enough for an agent to invoke this tool confidently.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no parameter-level guidance. It does not explain required fields, defaults, how project selection works, or how the parameters map to Azure DevOps concepts. With 10 parameters, this is a major gap and the description completely fails to compensate.

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 and resource: 'Report a bug to Azure DevOps'. The 'direct execution' phrase hints at a distinction from the sibling Report-Bug-To-Azure, but it does not fully explain what 'direct' means or how it changes behavior. It is specific enough for an agent to know the primary action, but sibling differentiation is weak.

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 given about when to use this tool versus Report-Bug-To-Azure. The '[EXPERIMENTAL]' tag and '(may hang)' warning imply caution but do not tell the agent when this direct variant should be preferred or avoided. The agent is left to infer the intended use case from the tool name alone.

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

Deploy Server