MCP Public APIs
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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 2 tools
The two tools have completely distinct purposes: one lists existing data (list_categories) and one updates the underlying data source (update_index). There is no overlap in functionality or ambiguity about when to use each tool.
Both tools follow a consistent verb_noun naming pattern (list_categories, update_index) with clear, descriptive names that indicate their actions and targets. The naming style is uniform throughout.
With only 2 tools, the server feels severely under-scoped for a 'Public APIs' domain. This minimal set lacks essential operations like searching APIs, getting API details, or filtering categories, which are core expectations for such a service.
The tool surface is significantly incomplete for a public APIs index. While it covers index maintenance (update_index) and basic listing (list_categories), it misses fundamental operations like retrieving specific API information, searching APIs by criteria, or accessing API endpoints, leaving agents unable to perform typical API discovery tasks.