Loading ToolBench

Reading the current corpus…

offline-chat MCP server · F · ToolBench

← Browse

offline-chat

github.com/ultrasardine/offline-chat

Terminal-based chatbot application using local Ollama models with RAG, database connections, and MCP tool integration

2026-07-28+STDIO6 tools

44/100

Definition Quality47

Protocol Readiness50

Supportability36

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Server has 6 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack consistent verb-noun structure (e.g., 'connect', 'disconnect', 'run-sql' use hyphens inconsistently). Descriptions are present but generic (avg ~60 chars, below 194-char baseline). Parameters lack descriptions in several tools (connect, disconnect, list-connections have empty properties). No output schemas documented. Error handling and recovery guidance absent. Security concern: connect tool exposes database credentials as parameters, violating secret-injection pattern. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels.

Tools (6)

connectwriteauthsource verified37/100

Connect to Oracle database. Must be called before running queries.

disconnectwritesource verified30/100

Disconnect from Oracle database

list-connectionsread onlysource verified38/100

List active database connections

run-sqlirreversibleauthsource verified50/100

Execute a SQL query and return results in CSV format

schema-informationread onlyauthsource verified57/100

Get database schema information (tables, columns, etc.)

web_searchread onlysource verified70/100

Search the web for current information. Use this when you need up-to-date information or facts you're not certain about.

Issues (5)

CRITICALsecret-injection ↗

Database credentials (username, password) exposed as tool parameters in 'connect' tool. Violates secret-injection pattern, credentials will be logged in traces and prompt history.

connect

HIGHtool-description ↗

Missing parameter descriptions in 'disconnect' and 'list-connections' tools (empty properties objects). LLMs cannot infer parameter meaning without descriptions.

disconnectlist-connections

HIGHtool ↗

No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., connection IDs for chaining).

web_searchconnectdisconnectrun-sqlschema-informationlist-connections

MEDIUMtool ↗

Tool names use inconsistent hyphenation ('run-sql', 'schema-information', 'list-connections') instead of snake_case verb_noun convention. Complicates LLM parsing.

run-sql

Recommendations

Move database credentials to server-side secret injection (environment variables or vault). Remove username/password from 'connect' parameters; accept only host, port, service_name, and resolve credentials server-side.
Add parameter descriptions to 'disconnect' and 'list-connections'. Example: disconnect → 'Closes the active database connection. No parameters required.' list-connections → 'Returns a list of active database connections with connection IDs, host, and status.'
Document output schemas for all tools. Example for 'list-connections': {type: 'array', items: {type: 'object', properties: {connection_id: {type: 'string'}, host: {type: 'string'}, status: {type: 'string'}}}}
Standardize tool names to snake_case verb_noun: 'run_sql', 'schema_information', 'list_connections'. Rename 'connect' to 'connect_database' for clarity.
Add tool annotations to all tools. Example: web_search → readOnlyHint: true; run_sql → destructiveHint: true (if UPDATE/DELETE allowed); connect → destructiveHint: true (state change).

Score history

Overall score trend

First recorded score · v2 rubric

44/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	44	2026-07-28+	v2