F
license-
qualityD
maintenanceProvides access to Rust crate documentation, search, and metadata from docs.rs and crates.io.
8
Ferritin — Rust documentation
by rs.ferritin
Server Details
Search and read Rust documentation for the standard library and any crate on crates.io
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jbr/ferritin
- GitHub Stars
- 33
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.3/5 across 2 of 2 tools scored. Lowest: 3.7/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: 'get' retrieves documentation for a specific item, while 'search' finds items or crates. There is no overlap between them.
Naming Consistency4/5
Both tool names are single verbs ('get', 'search'), which is simple and consistent. They deviate from a typical verb_noun pattern, but the convention is uniform.
Tool Count3/5
With only 2 tools, the server is minimal but appropriate for its narrow scope of Rust documentation lookup. Any fewer would be insufficient, and more could be added for robustness.
Completeness4/5
The server covers the core tasks of retrieving documentation and searching for items or crates. It lacks browsing or listing capabilities, but these are not essential for a focused doc lookup server.
Available Tools
2 toolsgetAInspect
Show documentation for a Rust item by path.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Item path, e.g. `serde::Deserialize` or `std::vec::Vec`. A crate segment may carry an `@`-suffixed semver requirement (not an exact version): `tokio@1::runtime::Runtime` serves the newest 1.x, while `tokio@=1.40` pins an exact release. |
Tool Definition Quality
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry behavioral information. It describes basic function but does not disclose side effects, permission needs, or error handling. Read-only nature is implied but not explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is a single, efficient sentence that conveys the tool's purpose with no extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter, no output schema), the description is adequate but could specify return format or error cases for completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a detailed parameter description including examples and format rules. The tool description adds no additional parameter information beyond the schema, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Show documentation for a Rust item by path', identifying the verb ('Show') and resource ('documentation for a Rust item'). It distinguishes from sibling 'search' by implying direct path-based lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives, or when not to use it. The parameter description adds format details but lacks usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchAInspect
Search for items within a crate's documentation, or — without a crate — discover which crate to use.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| crate | No | Crate to search within, optionally with an `@`-suffixed semver requirement (not an exact version): `serde`, `tokio@1` (newest 1.x), or `tokio@=1.40` to pin an exact release. **Omit only to discover which crate to use.** With `crate`, the search runs over that crate's full documentation — item names and prose. Without it, it searches a different, much shallower dataset: crates.io crate names, descriptions, and declared keywords. It returns crates, not items, and cannot see any crate's actual documentation. If you already know the crate name, always pass it. | |
| query | Yes | Search query — one or more complete words. With `crate`, matched against item names and documentation prose; without it, against crate names, descriptions, and declared keywords. |
Tool Definition Quality
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, but description fully explains dual behavior and limitations (shallower dataset without crate, cannot see actual documentation). Transparent about search scope.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single-sentence description that is front-loaded and efficient. Parameter descriptions are well-structured and without extraneous text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description covers both modes and parameter details comprehensively. Minor omission: no mention of output format, but still sufficient for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but parameter descriptions add significant meaning: semver requirement syntax, difference in search behavior with/without crate. Examples in schema further clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states two modes: searching within crate documentation and discovering which crate to use. Verb 'search' with specific targets, distinguishes from sibling 'get'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Parameter description explicitly says when to omit 'crate' (to discover crate) and when to include it (when crate name is known). Provides clear context for both use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityBmaintenanceEnables searching and fetching documentation pages from a wide range of programming languages, frameworks, game engines, and tools. Supports multiple sources and returns relevant documentation snippets.
Daipendencyofficial
AlicenseBqualityDmaintenanceGet the narrative and API documentation for the exact version of any of your dependencies. (Only Rust is supported at the moment.)11958MIT- AlicenseAqualityBmaintenanceAccess to 819+ documentation sources from devdocs.io with semantic search capabilities.9MIT