Loading ToolBench
An MCP server that provides current time in UTC and sends time data to a receiver socket
Three tools with minimal descriptions (10-30 chars, well below 50-200 char baseline). All tools lack parameter descriptions despite having parameters. No output schemas documented. get_current_time has empty input schema ({}), violating schema requirement. send_time_to_receiver performs a side effect (WRITE) but description does not warn of irreversibility. No error handling guidance. Tool names are clear (verb_noun pattern), but parameter documentation is absent entirely.
Get the current time in UTC.
Get the current time in a specific format.
Send the current time to the receiver at port 4321.
get_current_time has empty input schema ({}). Tool is non-functional for LLM parameter binding.
All three tools lack parameter descriptions. format_string parameter in get_formatted_time and send_time_to_receiver has no description explaining strftime syntax, valid formats, or constraints. LLMs cannot infer parameter meaning from names alone.
Tool descriptions are 10-30 characters (well below 50-200 char baseline). 'Get the current time in UTC.' lacks context for LLM selection. No explanation of when to use get_current_time vs get_formatted_time. No mention of return format or prerequisites.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
send_time_to_receiver is a destructive/side-effect tool (WRITE risk) but description does not warn of irreversibility or state modification. No confirmation step or dry-run option. Agents cannot distinguish safe reads from risky writes.
No output schemas documented. LLMs cannot plan downstream tool calls or extract structured data. Responses are free-text strings ('Current UTC time: ...'), requiring LLM parsing and wasting tokens.