F
licenseNot graded
qualityD
maintenanceProvides access to Rust crate documentation, search, and metadata from docs.rs and crates.io.
15
-
Ferritin — Rust documentation
by rs.ferritin
Server Details
Search and read Rust documentation for the standard library and any crate on crates.io
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jbr/ferritin
- GitHub Stars
- 33
Available Tools
2 toolsgetARead-onlyIdempotentInspect
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. |
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description is consistent. However, it adds no additional behavioral context such as error handling, return format, or interaction with external crates beyond what annotations already convey.
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?
The description is a single accurate sentence with no filler. Every word contributes to explaining the tool's core function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only lookup tool with rich parameter schema and annotations, the description is sufficient. The absence of an output schema is not a gap because the purpose ('Show documentation') makes the return type obvious.
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?
The schema description covers the 'path' parameter completely (100% coverage) with examples and semantics for version requirements. The tool description adds no extra meaning beyond restating that the path points to a Rust item, so the baseline of 3 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?
The description uses a specific verb ('Show documentation') and identifies the resource ('Rust item') and the key qualifier ('by path'). This clearly differentiates the tool from the sibling 'search', which is likely for finding items rather than direct retrieval.
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?
The description implies usage when you know an item's path, but it does not explicitly mention the sibling 'search' tool as an alternative for cases where the path is unknown. There is no explicit when-to-use versus when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchARead-onlyIdempotentInspect
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. |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations establish the tool as read-only, idempotent, and non-destructive. The parameter description adds valuable behavioral nuance beyond these annotations, explaining that without a crate the search runs over a 'much shallower dataset' and 'cannot see any crate's actual documentation.'
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?
The one-sentence description is extremely compact and front-loaded with the verb 'Search.' It efficiently communicates both usage modes with no wasted words or repetition of schema information.
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?
The definition is largely complete: annotations cover safety, the schema thoroughly explains parameter behavior, and the description clarifies the dual-mode nature. However, there is no output schema and the description does not state return format or pagination, which is a minor gap for a search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter descriptions are exceptionally detailed, including version syntax, examples, and mode-dependent behavior. The main description also contributes semantic meaning by indicating that `crate` is optional and changes the search target.
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?
The description clearly states the verb 'Search' and distinguishes two resources: items within a crate's documentation, or crates themselves when no crate is given. It effectively differentiates this search tool from the sibling 'get' tool by emphasizing discovery across documentation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The input schema provides explicit usage guidance: 'Omit only to discover which crate to use' and 'If you already know the crate name, always pass it.' This gives clear decision criteria for when to use each mode, though alternatives like the sibling 'get' tool are not mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
search4 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "crate": "serde", - "description": "Find deserialization items in serde", - "query": "deserialize" - } -]New value: +[ + { + "crate": "serde", + "description": "Find deserialization items in serde", + "query": "deserialize" + }, + { + "description": "Discover which crate to use for MQTT", + "query": "mqtt client" + } +] - changed
Input schema / properties / crate / descriptionPrevious value: -"Crate to search, optionally with an `@`-suffixed semver requirement (not\nan exact version): `serde`, `tokio@1` (newest 1.x), or `tokio@=1.40` to\npin an exact release."New value: +"Crate to search within, optionally with an `@`-suffixed semver\nrequirement (not an exact version): `serde`, `tokio@1` (newest 1.x), or\n`tokio@=1.40` to pin an exact release.\n\n**Omit only to discover which crate to use.** With `crate`, the search\nruns over that crate's full documentation — item names and prose.\nWithout it, it searches a different, much shallower dataset: crates.io\ncrate names, descriptions, and declared keywords. It returns crates,\nnot items, and cannot see any crate's actual documentation. If you\nalready know the crate name, always pass it." - changed
Input schema / properties / query / descriptionPrevious value: -"Search query — one or more words matched against item names and prose."New value: +"Search query — one or more complete words. With `crate`, matched\nagainst item names and documentation prose; without it, against crate\nnames, descriptions, and declared keywords." - changed
Input schema / requiredPrevious value: -[ - "crate", - "query" -]New value: +[ + "query" +]
2 tool updates
- First observed
get - First observed
search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
DevDocs.io keyless docs index + entry search + content (Angular, MDN, Rust, etc.).
Get up-to-date, version-specific documentation and code examples from official sources directly in…
Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues.
Retrieve information from the Medusa documentation to assist you with your Medusa development.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables 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.)12257MIT- AlicenseAqualityBmaintenanceAccess to 819+ documentation sources from devdocs.io with semantic search capabilities.9MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: get fetches docs for a known path, while search discovers items or crates. There is no overlap or ambiguity.
Naming Consistency5/5
Both tool names are single lowercase verbs (get, search), following a consistent, predictable pattern. No mixed conventions or inconsistent styles.
Tool Count3/5
With only 2 tools, the set feels thin for a documentation server that might benefit from listing or browsing capabilities. However, the tools cover the core actions of fetching and searching, so the count is borderline acceptable.
Completeness4/5
The tool surface covers the primary read-only operations for Rust documentation: retrieving specific items and searching for them. Minor gaps exist, such as enumerating modules or listing crate versions, but they are not critical and can be worked around.