FastMCP MCP 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 |
| fetch_pageA | Fetch the content of a web page as markdown using Jina Reader. Args: url: The URL of the page to fetch. |
| search_docsB | Search FastMCP documentation for the given query. Args: query: The search 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 3 tools
Each tool performs a unique, clearly defined function with no overlap between arithmetic, web fetching, and documentation search. An agent would have no difficulty selecting the appropriate tool.
Tool names are short, lowercase, and mostly follow a verb_noun pattern (fetch_page, search_docs). The lone exception is 'add', which is a bare verb, but it is still clear and consistent in style.
With only 3 tools, the server is on the lighter side, but the small set is still reasonable for a general-purpose utility server. Each tool earns its place, though the collection feels somewhat sparse.
The tools are unrelated to a single coherent domain, making it difficult to assess what complete coverage would look like. There are no obvious lifecycle operations (e.g., update or delete) and the set appears to be a collection of unconnected utilities, leaving significant gaps for any specific purpose.