MCP server that composes and aggregates tools, resources, and prompts from multiple target MCP servers into a single unified interface
McGravity exposes only 1 tool ('echo') with critically deficient definitions. The tool has a bare description ('Tool echo') that provides zero context for LLM selection. The input schema is visible but parameter 'message' lacks a description (null value in the schema). No output schema is documented. The tool does not follow verb_noun naming (should be 'echo_message' or similar). No error handling, no parameter constraints, no guidance on when to use this tool. This is a minimal example server, not production-grade.
Tool echo
Tool description is trivial ('Tool echo'), under 20 characters, provides no context for LLM selection or when to use the tool.
Parameter 'message' has null description in schema, LLM cannot infer what kind of message, format, or constraints apply.
No output schema documented, LLM cannot predict what fields the tool returns or plan downstream operations.
Tool name 'echo' is generic and does not start with an action verb, should be 'echo_message' or 'process_message' to clarify intent.
No error handling or recovery guidance, if the tool fails, the LLM has no actionable next step.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |