Loading ToolBench

Reading the current corpus…

dotnetclaw MCP server · D · ToolBench

dotnetclaw

A .NET-based AI agent framework with Blazor web UI, Telegram bot integration, workflow engine, and MCP support for autonomous task execution

<=2025-11-258 tools

51/100

Definition Quality73

Protocol Readiness32

Supportability26

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

DotnetClaw's 8 job-scheduling tools have clear verb-noun naming (schedule_job, list_jobs, delete_job) and reasonable descriptions (avg ~120 chars). All tools have input schemas with typed parameters. However, parameter descriptions are sparse, many lack detail on constraints, formats, or dependencies. Output schemas are not documented. Error handling guidance is absent. The tools follow a consistent pattern but lack the depth needed for A-grade quality.

Tools (8)

delete_jobdestructivesource verified75/100

Permanently delete a scheduled job by its ID.

disable_jobwritesource verified70/100

Pause a job without deleting it. It can be re-enabled later.

enable_jobwritesource verified70/100

Re-enable a previously disabled job.

get_jobread onlysource verified68/100

Get full details and the last result for a specific job by its ID.

list_jobsread onlysource verified77/100

List all scheduled background jobs (enabled and disabled).

run_job_nowwritesource verified72/100

Execute a job immediately, regardless of its schedule.

schedule_jobwritesource verified77/100

Schedule a recurring background job using a CRON expression. The job will run the given prompt through the agent on the specified schedule. When the user describes a schedule in natural language (e.g. 'every morning at 8:00', 'every Monday at noon', 'twice a day') convert it to a standard 5-part CRON expression (minute hour dom month dow) before calling this function. Returns the new job ID.

Issues (5)

HIGHtool ↗

Output schemas not documented. LLMs cannot plan downstream calls or extract job IDs, status, or results without knowing response structure.

schedule_jobschedule_oncelist_jobsget_job

HIGHconstrained-input ↗

Parameter descriptions lack constraint details. 'jobId' is described as '8-character job ID' but no validation guidance for LLM. 'cronExpression' lacks format examples or validation rules beyond the single example.

schedule_jobschedule_onceget_jobdelete_jobenable_jobdisable_jobrun_job_now

HIGHrecovery-guide ↗

No error handling guidance. Tools do not document what happens on invalid CRON, missing job ID, or permission failures. LLM has no recovery path.

schedule_jobschedule_onceget_jobdelete_jobenable_jobdisable_jobrun_job_now

Recommendations

Document output schemas for all tools. E.g., schedule_job returns {jobId: string, name: string, cronExpression: string, createdAt: ISO8601}. list_jobs returns {jobs: [{jobId, name, cronExpression, enabled, lastRun, nextRun}], total: number}.
Enhance parameter descriptions with validation rules and examples. E.g., 'cronExpression: Standard 5-part CRON (minute hour dom month dow). Examples: "0 8 * * *" (daily 08:00 UTC), "0 9 * * 1" (Mondays 09:00 UTC). Invalid expressions will be rejected with a clear error message.'
Add error handling guidance to each tool description. E.g., 'If the job ID is not found, the tool returns a 404 error with available job IDs. If the CRON expression is invalid, the tool returns a validation error listing the syntax rules.'
Implement a confirm_delete_job tool or add a 'dryRun' parameter to delete_job to prevent accidental permanent deletion of scheduled jobs.
Clarify the distinction between enable_job/disable_job and the 'enabled' field in list_jobs. Document what 'disabled' means (paused but not deleted) and whether disabled jobs still appear in list_jobs output.

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

51/100

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