A FastAPI-based MCP server platform that integrates multiple backend services and exposes them as MCP tools via HTTP/SSE transport
Server exposes 7 tools with basic schemas and descriptions. Most tools have action-verb names (list_, get_, create_, update_, delete_, search_) and parameter descriptions. However, descriptions are generic and lack LLM-optimization guidance. Parameter schemas are present but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling is minimal, tools reference HTTP 404 but provide no recovery guidance. Tool 7 (test_endpoint) has a Chinese description and no parameters, suggesting incomplete localization. Overall structure is functional but falls short of production-grade quality.
Create a new item in the database. Returns the created item with its assigned ID.
Delete an item from the database. Raises a 404 error if the item does not exist.
Get a specific item by its ID. Raises a 404 error if the item does not exist.
List all items in the database. Returns a list of items, with pagination support.
Search for items with various filters. Returns a list of items that match the search criteria.
一个用来打招呼的工具
Update an existing item. Raises a 404 error if the item does not exist.
test_endpoint has Chinese description ('一个用来打招呼的工具') and no input schema. Violates naming clarity and description requirements.
No output schemas documented for any tool. LLMs cannot infer response structure, forcing them to guess field names and types for downstream tool chaining.
Parameter descriptions lack constraints. 'skip' and 'limit' have no min/max bounds; 'q' (search query) has no length limit; 'min_price'/'max_price' have no relationship documented.
Error handling is minimal. Tools mention '404 error' but provide no recovery guidance (e.g., 'Try search_items() to find the item first').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
create_item and update_item require 'id' in the item object, but it's unclear if the client must generate it or the server assigns it. Ambiguous parameter relationships.