relay + mcp (prism + laravel boost / laravel mcp) -> ollama qwen3:0.6b

[Karl-H0110]

Prism\Prism\Exceptions\PrismException

Sending to model (qwen3:0.6b) failed: HTTP request returned status code 400

at vendor\prism-php\prism\src\Exceptions\PrismException.php:65
61▕ }
62▕
63▕ public static function providerRequestError(string $model, Throwable $previous): self
64▕ {
➜ 65▕ return new self(vsprintf('Sending to model (%s) failed: %s', [
66▕ $model,
67▕ $previous->getMessage(),
68▕ ]), previous: $previous);
69▕ }

1 vendor\prism-php\prism\src\Providers\Provider.php:73
Prism\Prism\Exceptions\PrismException::providerRequestError()

2 vendor\prism-php\prism\src\Text\PendingRequest.php:69
Prism\Prism\Providers\Provider::handleRequestException()

the ai can't use laravel mcp tools

edit:

Failed to fetch tools from MCP server 'laravel-boost': JSON-RPC error: Invalid params: "id" must be an integer or null if present. (code: -32602) -> when i use http / stdio

[ju5t]

I think this is a bug. Not entirely sure where this is coming from, because after making some changes I got a similar issue with laravel/mcp, so it's not strictly a relay thing.

The JSON spec says that id's can be string by the way:

id
An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

[Karl-H0110]

I think this is a bug. Not entirely sure where this is coming from, because after making some changes I got a similar issue with laravel/mcp, so it's not strictly a relay thing.

The JSON spec says that id's can be string by the way:

id
An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

it comes from :

Prism\Relay\Transport\StdioTransport / http (depends on what u use in config)

btw , the problem is "id" must be integer

the relay code
` protected function prepareRequest(string $method, array $params = []): void
{
if (! $this->inputStream instanceof \Symfony\Component\Process\InputStream || ! $this->process instanceof \Symfony\Component\Process\Process) {
throw new TransportException('Transport not properly initialized');
}

    $this->requestId++;

    $requestPayload = [
        'jsonrpc' => '2.0',
        'id' => (string) $this->requestId,
        'method' => $method,
        'params' => $params,
    ];

    // Handle special case for tools/list endpoint which requires an object
    if ($method === 'tools/list' && $params === []) {
        $requestPayload['params'] = new \stdClass;
    }

    $jsonRequest = json_encode($requestPayload, JSON_UNESCAPED_SLASHES).PHP_EOL;

    $this->inputStream->write($jsonRequest);
    $this->process->clearErrorOutput();
    $this->process->clearOutput();
}`

look at "'id' => (string) $this->requestId," it's return string not null or int

btw , i can edit this issue but after that it gives me alot of things , also stdio not working with laravel tools ,

the problem is the "relay doesn't support laravel boost or laravel mcp as a http or stdio" , (i didn't try external mcp servers)

also tysm for reading 😊

[hipig]

I think this is a bug. Not entirely sure where this is coming from, because after making some changes I got a similar issue with laravel/mcp, so it's not strictly a relay thing.
The JSON spec says that id's can be string by the way:

id
An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

it comes from :

Prism\Relay\Transport\StdioTransport / http (depends on what u use in config)

btw , the problem is "id" must be integer

the relay code ` protected function prepareRequest(string $method, array $params = []): void { if (! $this->inputStream instanceof \Symfony\Component\Process\InputStream || ! $this->process instanceof \Symfony\Component\Process\Process) { throw new TransportException('Transport not properly initialized'); }

    $this->requestId++;

    $requestPayload = [
        'jsonrpc' => '2.0',
        'id' => (string) $this->requestId,
        'method' => $method,
        'params' => $params,
    ];

    // Handle special case for tools/list endpoint which requires an object
    if ($method === 'tools/list' && $params === []) {
        $requestPayload['params'] = new \stdClass;
    }

    $jsonRequest = json_encode($requestPayload, JSON_UNESCAPED_SLASHES).PHP_EOL;

    $this->inputStream->write($jsonRequest);
    $this->process->clearErrorOutput();
    $this->process->clearOutput();
}`

look at "'id' => (string) $this->requestId," it's return string not null or int

btw , i can edit this issue but after that it gives me alot of things , also stdio not working with laravel tools ,

the problem is the "relay doesn't support laravel boost or laravel mcp as a http or stdio" , (i didn't try external mcp servers)

also tysm for reading 😊

The problem lies with laravel-mcp; the current v0.1.1 version imposes strict limits on request id, see JsonRpcRequest. This restriction has been removed in the unreleased higher version v0.1.2-beta. This issue is not caused by Relay; we need to wait for laravel-mcp to release a new version, and boost can be updated.

[Karl-H0110]

I think this is a bug. Not entirely sure where this is coming from, because after making some changes I got a similar issue with laravel/mcp, so it's not strictly a relay thing.
The JSON spec says that id's can be string by the way:

id
An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

it comes from :

Prism\Relay\Transport\StdioTransport / http (depends on what u use in config)

btw , the problem is "id" must be integer
the relay code ` protected function prepareRequest(string $method, array $params = []): void { if (! $this->inputStream instanceof \Symfony\Component\Process\InputStream || ! $this->process instanceof \Symfony\Component\Process\Process) { throw new TransportException('Transport not properly initialized'); }

    $this->requestId++;

    $requestPayload = [
        'jsonrpc' => '2.0',
        'id' => (string) $this->requestId,
        'method' => $method,
        'params' => $params,
    ];

    // Handle special case for tools/list endpoint which requires an object
    if ($method === 'tools/list' && $params === []) {
        $requestPayload['params'] = new \stdClass;
    }

    $jsonRequest = json_encode($requestPayload, JSON_UNESCAPED_SLASHES).PHP_EOL;

    $this->inputStream->write($jsonRequest);
    $this->process->clearErrorOutput();
    $this->process->clearOutput();
}`

look at "'id' => (string) $this->requestId," it's return string not null or int
btw , i can edit this issue but after that it gives me alot of things , also stdio not working with laravel tools ,
the problem is the "relay doesn't support laravel boost or laravel mcp as a http or stdio" , (i didn't try external mcp servers)
also tysm for reading 😊

The problem lies with laravel-mcp; the current v0.1.1 version imposes strict limits on request id, see JsonRpcRequest. This restriction has been removed in the unreleased higher version v0.1.2-beta. This issue is not caused by Relay; we need to wait for laravel-mcp to release a new version, and boost can be updated.

we doesn't know the release date right? , okay np , tysm for replied