Loading ToolBench
Rust expert MCP server — live access to rust-lang GitHub, The Book, Reference, Nomicon, RFCs, compiler errors, and crates.io
Strong foundation with 13 well-named, verb-prefixed tools and comprehensive parameter schemas using schemars. All tools have descriptions (avg ~120 chars) and typed parameters with descriptions. However, output schemas are not documented in the source, LLMs cannot see what fields to expect from responses. No error handling guidance, no recovery patterns, and no tool annotations (readOnlyHint, idempotentHint). Parameter descriptions are good but lack format constraints (e.g., 'limit: 1 - 30' stated in description but not as JSON Schema min/max). No pagination metadata documented. Missing composition guidance for multi-step workflows.
Get detailed explanation of a Rust compiler error code. Includes the error description, common causes, and examples from the official Rust error index.
Fetch a chapter from "The Rust Programming Language" book. Comprehensive guide to Rust covering ownership, borrowing, lifetimes, traits, smart pointers, concurrency, and more.
Fetch metadata and information about a crate from crates.io. Includes description, documentation link, repository, download stats, and version history.
Fetch a section from "The Rustonomicon" (Rust Unsafe Code Guidelines). Advanced documentation on unsafe Rust, memory layout, FFI, and low-level details.
Fetch a section from the Rust Reference. Detailed technical documentation of Rust language features, syntax, semantics, and behavior.
Fetch a file from any rust-lang GitHub repository. Supports source code, documentation, configuration, and any other file type.
Fetch a specific Rust Enhancement Proposal (RFC) by number. RFCs document major language and library changes, design decisions, and accepted proposals.
Output schemas not documented. LLMs cannot see what fields responses contain (e.g., does search_rust_source return 'url' or 'html_url'? Does get_crate return 'downloads' or 'recent_downloads'?). This forces agents to guess field names and risks extraction errors.
No error handling guidance. Tools return raw HTTP errors or API failures with no recovery hints. E.g., if GitHub API rate-limits, the LLM sees a 403 but doesn't know to retry later or use a different search strategy.
Parameter constraints stated in descriptions but not enforced in JSON Schema. 'limit: 1 - 30' is prose; should be minItems/maxItems in schema. LLMs may pass limit=100 and fail.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | <=2025-11-25 | v2 |
Fetch a section from "Rust By Example". Practical, runnable examples demonstrating Rust language features and standard library usage.
Fetch the Rust edition guide for a specific year. Explains edition features, migration guides, and compatibility information.
List rust-lang GitHub repositories with metadata. Shows repository names, descriptions, star counts, primary language, and update timestamps.
Search issues and pull requests across rust-lang GitHub repositories by title, body, and metadata. Find discussions, bug reports, feature requests, and RFCs.
Search Rust Enhancement Proposals (RFCs) by keywords in file names and content. Find discussions about language features, library additions, and design decisions.
Search source code across all rust-lang GitHub repositories. Finds implementations, usages, and examples in rustc (the compiler), the standard library, Cargo, Clippy, rustfmt, rustdoc, and every other official Rust project. Supports any code search query.
No tool annotations. All tools are read-only (safe to retry, no side effects), but this is not declared via readOnlyHint. Agents cannot distinguish safe tools from destructive ones.
Pagination not documented. search_rust_source and search_issues accept 'limit' but no 'offset' or 'cursor'. Unclear if results are paginated or if limit=30 returns all 30 or stops early.