sufetch
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": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_apisA | List all available API specifications with their metadata |
| get_api_infoC | Get detailed information about a specific API |
| search_endpointsC | Search for API endpoints by query, method, or tags |
| get_endpoint_detailsA | Get complete details and usage example for a specific endpoint |
| get_schema_detailsC | Get details about a schema/model definition |
| generate_code_exampleB | Generate a complete TypeScript code example for an endpoint |
| get_quickstartA | Generate a quickstart guide with common operations for an API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| quickstart | Get started with an API - installation, setup, and common examples |
| implement-endpoint | Generate implementation guide for a specific endpoint with full code |
| explore-api | Interactive guide to explore an API with focus on specific area |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear and distinct purpose: code generation, API info, endpoint details, quickstart, schema details, listing, and searching. No overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., generate_code_example, list_apis). The naming is predictable and easy to understand.
With 7 tools, the server is well-scoped. It covers all necessary operations for exploring API documentation without being bloated or too minimal.
The tool surface covers listing, searching, and retrieving details for APIs, endpoints, schemas, code examples, and quickstarts. However, there is no tool to list all schemas directly, which is a minor gap.