Modern AI-powered API client with support for HTTP, GraphQL, WebSocket, gRPC, Mock Servers, SSE, and MCP protocols
Portiq exposes 7 tools with basic schemas and descriptions, but falls short of production quality. Tool names lack consistent verb-noun structure (mockStart/mockStop vs sendAutoHttpRequest). Descriptions are present but generic (10-50 chars for most), providing minimal context for LLM selection. Input schemas exist but lack depth: no enums for constrained values (e.g., HTTP methods are free-form strings), no parameter descriptions beyond type hints, and no documented output schemas. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. The mock server tools (mockStart, mockUpdateRoutes) accept 'routes' as an array with no schema for route structure, forcing LLMs to guess the format. HTTP request tools lack timeout validation, header constraints, and response documentation. No security considerations visible (e.g., no mention of secret injection for auth headers). Overall, definitions are skeletal, sufficient to invoke but insufficient for reliable agent reasoning.
List all running mock servers
Start a new mock server with specified port, name, and routes
Stop a running mock server by ID
Update routes on a running mock server
Send an HTTP request using automatic protocol detection (HTTP/1.1, HTTP/2, or fetch)
Send an HTTP/1.1 request
Send an HTTP/2 request
No output schemas documented. LLMs cannot plan downstream calls or extract response fields. All 7 tools lack return type documentation.
Route structure for mock servers is undocumented. 'routes' parameter accepts an array with no schema, forcing LLMs to guess format (path, method, response, status code, etc.).
HTTP method parameter is free-form string with no enum constraint. LLMs may pass invalid methods (FETCH, RETRIEVE, etc.) instead of valid HTTP verbs.
No error handling guidance. Tools lack recovery hints, retryability classification, or actionable error messages. LLMs cannot self-correct on failure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Descriptions are too brief (30-45 chars). Lack context on WHEN to use each tool, prerequisites, and side effects. 'Send an HTTP/1.1 request' does not explain when to choose HTTP/1.1 vs HTTP/2 vs auto.