Menu
Rename MCP tool parameters when the wire schema drifted from semantic intent.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Investigate .NET CI failures using the hlx CLI tool via bash. USE FOR: checking Helix job status, searching build logs, downloading test results, AzDO build timeline analysis — when MCP tools aren't loaded, when the MCP server isn't configured or fails to start, or when scripting with JSON output and jq. DO NOT USE FOR: tasks where Helix/AzDO MCP tools are already available in context (prefer ci-analysis skill when MCP server is loaded). INVOKES: bash (hlx CLI commands with --json output).
{what this skill teaches agents}
Audit pattern for comparing WorkItemSummary (list API) fields against WorkItemDetails (per-item API) after a Helix.Client SDK bump
Domain-layer normalizer + JSON-stable cache key pattern for filter types with server-side defaults and case-insensitive fields.
Strict unknown-parameter rejection for MCP tools: Stage A (UnmappedMemberHandling.Disallow) + Stage B (did-you-mean CallToolFilter).
Audit MCP/CLI tool parameter surface against underlying REST API capabilities to find silently-dropped params.
| name | mcp-param-rename |
| description | Rename MCP tool parameters when the wire schema drifted from semantic intent. |
| domain | mcp-server-design |
| confidence | medium |
| source | earned |
Use this when an MCP tool parameter name is part of the caller-visible JSON schema and no longer matches the semantic contract.
buildIdOrUrl.tools/list exposes the new parameter, a call with the new parameter succeeds, and the old parameter fails with an explicit isError response rather than silent null.