FastMCP Documentation Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addA | Add two numbers |
| hash_textB | Hash a string using SHA-256 |
| scrape_pageB | Scrape the content of a web page using Jina reader |
| search_docsB | Search FastMCP documentation for a query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: add performs arithmetic, hash_text handles cryptographic hashing, scrape_page extracts web content, and search_docs searches documentation. The functions are so different that misselection is highly unlikely.
The naming is inconsistent with mixed conventions: add uses a simple verb, hash_text uses verb_noun, scrape_page uses verb_noun, and search_docs uses verb_noun. There is no uniform pattern, and the single-word 'add' deviates significantly from the others.
With 4 tools, the count is borderline for the server's stated purpose of 'Documentation Search Server'—only one tool directly supports this, while others are unrelated utilities. This feels thin and misaligned with the domain, though not extreme.
For a documentation search server, there is a significant gap: only search_docs directly serves the purpose, while add, hash_text, and scrape_page are unrelated. This lacks coverage for typical documentation workflows like browsing, filtering, or managing documentation, likely causing agent failures.