MCP Server By TestMu AI

Build and Analyze App

buildLocalAppForAnalysis

Read-only

Returns step-by-step instructions to build and serve a local web app and open a TestMu AI tunnel to it, so its accessibility can then be scanned with analyzeAppViaTunnel. It does not build, run or scan anything itself, and never includes the access key.

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": {
      "codebasePath": "<codebasePath>",
      "port": "<port>"
    },
    "name": "buildLocalAppForAnalysis"
  }
}

Input Schema

Name	Required	Description
`port`	Yes	Port to host the app locally
`codebasePath`	Yes	Absolute path to the codebase directory
`customBuildCommand`	No	Custom build command (optional, e.g., npm run build)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The annotations already declare a safe read-only, non-destructive, closed-world operation. The description adds valuable behavioral context beyond annotations: it returns instructions rather than executing anything, and it never includes the access key.

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 compact and front-loaded, starting with what the tool returns. Every clause adds useful scope or safety information without redundancy.

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

Completeness5/5

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

Given the read-only annotations, full schema coverage, and absence of an output schema, the description covers the essential gap by explaining that the tool returns instructions and does not execute actions. Nothing critical for correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents port, codebasePath, and customBuildCommand. The description does not add parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 a specific verb and resource: it returns step-by-step instructions to build and serve a local web app and open a TestMu AI tunnel. It explicitly distinguishes this from analyzeAppViaTunnel by saying it does not build, run, or scan anything itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly positions the tool as a preparatory step before using analyzeAppViaTunnel for accessibility scanning. It also states a key limitation (it does not perform the build, run, or scan), but does not give explicit when-not-to-use conditions such as when the app is already served.

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

All MCP Server By TestMu AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?