Loading ToolBench

Reading the current corpus…

krayin-mcp MCP server · F · ToolBench

krayin-mcp

TypeScript template for building Model Context Protocol (MCP) servers & clients. Features production-ready utilities, stdio/HTTP transports (with JWT auth), examples, and type safety. Ideal starting point for creating MCP-based applications.

<=2025-11-25STREAMABLE_HTTP2 tools

49/100

Definition Quality43

Protocol Readiness65

SupportabilityNot measured-

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Server has 2 tools with mixed quality. echo_message is well-defined with complete Zod schema, proper parameter descriptions, and clear constraints (minLength, maxLength, enums, defaults). krayin_mcp_tool lacks visible schema definition and detailed parameter documentation, only a generic description is provided. The echo tool demonstrates good practices (constraints, type safety, structured output), but the second tool is underspecified. Overall: solid foundation for one tool, but incomplete coverage for the other.

Tools (2)

echo_messageread only50/100

Echoes back a message with optional formatting (uppercase/lowercase) and repetition. Supports timestamp inclusion in response.

krayin_mcp_toolwriteauth25/100

Tool for interacting with Krayin CRM system. Handles CRM operations and integrations.

Issues (5)

CRITICALtool ↗

krayin_mcp_tool has no visible input schema. Tool registration file (src/mcp-server/tools/krayinMcpTool/registration.ts) not provided in source code sample. Cannot verify parameter types, constraints, or descriptions.

krayin_mcp_tool

HIGHtool-description ↗

krayin_mcp_tool description is generic ('Tool for interacting with Krayin CRM system. Handles CRM operations and integrations.') and does not explain WHAT operations, WHEN to use it, or what it returns. LLMs cannot determine when to select this tool.

krayin_mcp_tool

HIGHtool ↗

krayin_mcp_tool name is vague. 'krayin_mcp_tool' does not follow verb_noun convention (e.g., 'get_crm_contact', 'create_crm_lead'). LLMs cannot infer the action from the name alone.

krayin_mcp_tool

LOWtool ↗

echo_message naming could be more specific. 'echo_message' is acceptable but does not follow strict verb_noun pattern. Consider 'format_and_repeat_message' or split into separate tools if formatting and repetition are distinct concerns.

Recommendations

Provide complete source code for krayin_mcp_tool registration, including input schema (Zod or JSON Schema), parameter descriptions, and return type documentation.
Rewrite krayin_mcp_tool description to answer: What CRM operations does it support? When should the LLM call it instead of other tools? What does it return? Example: 'Create, retrieve, update, or delete Krayin CRM contacts. Use this to manage customer records. Returns contact ID, name, email, and status.'
Rename krayin_mcp_tool to a verb_noun pattern reflecting its primary action, e.g., 'manage_crm_contact', 'create_crm_lead', or 'search_crm_records'. If it handles multiple distinct operations, split into separate tools.
Document the output schema for both tools in code comments or JSDoc. For echo_message, explicitly show the JSON structure returned in CallToolResult.content[].text. For krayin_mcp_tool, define all fields returned (IDs, timestamps, status codes).
Add error handling guidance to both tools. Example for echo_message: 'If message exceeds 1000 characters, return error with guidance to split into multiple calls.' For krayin_mcp_tool: 'If contact not found, return available search options to help the LLM retry.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

49/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	49	<=2025-11-25	v2