Run any Skill in Manus with one click

Get Started

mcp-calltoolfilter-tests

Stars3

Forks3

UpdatedJune 7, 2026 at 03:20

Test MCP CallToolFilter behavior with real CallToolRequestParams and McpServerTool invocation.

Installation

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.

Run Skill in Manus

Source

lewing

lewing/helix.mcp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	mcp-calltoolfilter-tests
description	Test MCP CallToolFilter behavior with real CallToolRequestParams and McpServerTool invocation.
domain	mcp-testing
confidence	high
source	earned

Context

Use this when validating McpServerOptions.Filters.Request.CallToolFilters, especially filters that mutate inbound CallToolRequestParams.Arguments before SDK parameter binding.

Pattern

Unit-test the filter by wrapping a capture handler and asserting the request's argument dictionary after the filter runs.
For binding behavior, wrap McpServerTool.InvokeAsync created from the real attributed tool method; this exercises SDK binding instead of a helper-only path.
Construct RequestContext<CallToolRequestParams> with a real CallToolRequestParams { Name = toolName, Arguments = ... } and JSON-backed JsonElement values via JsonSerializer.SerializeToElement.
Assert both success routing and failure wrapping: missing required arguments should still become the repo's structured McpException.

Example Scenarios

Alias-only argument normalizes before binding.
Canonical parameter wins when canonical and alias are both present.
Multiple aliases have documented precedence.
Non-standard alias casing is accepted when the alias table is case-insensitive.
Test with realistic value types from telemetry, not just sanitized strings; numeric JsonElement aliases should be covered when callers send IDs as JSON numbers.

More from this repository

same repository

helix-cli

lewing/helix.mcp

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).

2026-07-203

skill-name

lewing/helix.mcp

{what this skill teaches agents}

2026-07-203

helix-sdk-summary-vs-details

lewing/helix.mcp

Audit pattern for comparing WorkItemSummary (list API) fields against WorkItemDetails (per-item API) after a Helix.Client SDK bump

2026-06-253

centralized-filter-normalization

lewing/helix.mcp

Domain-layer normalizer + JSON-stable cache key pattern for filter types with server-side defaults and case-insensitive fields.

2026-06-253

mcp-strict-param-rejection

lewing/helix.mcp

Strict unknown-parameter rejection for MCP tools: Stage A (UnmappedMemberHandling.Disallow) + Stage B (did-you-mean CallToolFilter).

2026-06-243

azdo-rest-param-surface-audit

lewing/helix.mcp

Audit MCP/CLI tool parameter surface against underlying REST API capabilities to find silently-dropped params.

2026-06-243

name	mcp-calltoolfilter-tests
description	Test MCP CallToolFilter behavior with real CallToolRequestParams and McpServerTool invocation.
domain	mcp-testing
confidence	high
source	earned

Context

Use this when validating McpServerOptions.Filters.Request.CallToolFilters, especially filters that mutate inbound CallToolRequestParams.Arguments before SDK parameter binding.

Pattern

Unit-test the filter by wrapping a capture handler and asserting the request's argument dictionary after the filter runs.
For binding behavior, wrap McpServerTool.InvokeAsync created from the real attributed tool method; this exercises SDK binding instead of a helper-only path.
Construct RequestContext<CallToolRequestParams> with a real CallToolRequestParams { Name = toolName, Arguments = ... } and JSON-backed JsonElement values via JsonSerializer.SerializeToElement.
Assert both success routing and failure wrapping: missing required arguments should still become the repo's structured McpException.

Example Scenarios

Alias-only argument normalizes before binding.
Canonical parameter wins when canonical and alias are both present.
Multiple aliases have documented precedence.
Non-standard alias casing is accepted when the alias table is case-insensitive.
Test with realistic value types from telemetry, not just sanitized strings; numeric JsonElement aliases should be covered when callers send IDs as JSON numbers.