Ics Ap Apis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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 |
|---|---|
| api_endpointD | 请根据 RapidAPI 页面手动添加端点信息 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'api_endpoint' has a distinct purpose of adding endpoint information from RapidAPI pages.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'api_endpoint' follows a clear noun-based pattern, and there are no other tools to create inconsistency.
A single tool is too few for a server named 'Ics Ap Apis MCP Server', which suggests a broader API management or integration scope. One tool cannot adequately cover operations like listing, updating, or deleting endpoints, making it feel incomplete and thin.
The tool set is severely incomplete for an API-related server. It only allows adding endpoints manually, with no tools for retrieving, modifying, deleting, or managing existing endpoints, creating significant gaps that will hinder agent workflows.