Skip to content

--load: scenario file with a weighted mix of tools, resources/read and prompts/get #2839

Closed

Description

@CloneOfAlex

Which client?

All / shared core

The problem

Real traffic is not one tool called with fixed arguments. --load can only drive a single tools/call, so a server's behaviour under a realistic mix (several tools, resources/read, prompts/get) cannot be measured.

Solution you have in mind (optional)

--load-scenario scenario.json listing steps with a weight each, e.g. [{"method":"tools/call","tool":"search","args":{...},"weight":7},{"method":"resources/read","uri":"...","weight":3}]. The summary breaks down counts, errors and latency per step plus the total.

Alternatives or workarounds you have tried

Running several --load processes in parallel, one per tool — which multiplies connections and gives no combined view.

Already built it locally?

No response

Before you submit

  • I searched existing issues and this is not a duplicate.
  • This is a request for the Inspector itself, not for the MCP specification or an SDK.

Activity

  1. cliffhall commented on Oct 29, 2026

    @cliffhall
    Member

    Triage: Priority Low (total 4)

    • Severity 2 — a richer --load workload; parallel runs are a workaround
    • Urgency 2 — wanted eventually, nothing blocked on it
    • Bonuses: none (no milestone, assignee, epic, engagement or reporter-set priority)

    Board: #28, Status Incoming (awaiting maintainer review — no milestone yet).

  2. added this to the v2.15.0 milestone on Oct 29, 2026
  3. self-assigned this
    on Nov 5, 2026
  4. cliffhall commented on Nov 5, 2026

    @cliffhall
    Member

    Shipped in #2896 (merge 37e4df6).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature requestv2Issues and PRs for v2

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions