Turn any JS/TS function into a WebMCP tool — function-first, type-safe, lean. One line: webmcp(fn) still callable, auto-registers with React lifecycle or globally.
simple-webmcp is a client-side SDK for wrapping JS/TS functions as WebMCP tools, not a server. Tool definitions are inferred from examples rather than explicitly registered in source code. The 4 tools shown have inconsistent schemas and descriptions across files. searchCustomers appears twice with different parameter descriptions (one includes 'ID', the other omits it). Descriptions are minimal (10-30 chars), below the 50-200 char baseline for LLM-optimized docs. No output schemas documented. No error handling guidance visible. Parameters lack depth, 'query' and 'limit' have basic descriptions but no format constraints or examples. The framework appears designed for client-side tool wrapping rather than server-side MCP implementation, which limits protocol readiness.
Add product to cart
Search customers in current account
Search customers
Update customer information
Tool definitions inferred from examples, not explicitly registered in source. Cannot verify actual tool registration mechanism or schema enforcement.
Duplicate tool name 'searchCustomers' with inconsistent parameter descriptions across files (vanilla.js vs with-react.tsx). One includes 'ID' in query description, the other omits it.
All tool descriptions are under 20 characters (10-35 chars observed). Baseline for LLM-optimized descriptions is 50-200 chars. Descriptions lack context for when/why to use each tool.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2025-06-18+ | v2 |
Parameter descriptions lack format constraints, ranges, or examples. 'query' parameter has no guidance on accepted formats (name vs email vs ID). 'limit' has min/max but no rationale.