Celebrity By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 | |
| PORT | No | 不适用 | |
| 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1celebrityD | API Ninjas Celebrity API endpoint. |
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, as there are no other tools to compare it to. The single tool's purpose is clearly defined as accessing the Celebrity API endpoint, leaving no room for confusion.
Since there is only one tool, naming consistency is inherently perfect. There are no other tool names to compare against, so no inconsistencies can arise in patterns or conventions.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or thin interface. For a celebrity API, one tool might cover basic queries but lacks operations like search, filtering, or detailed retrieval, making it feel under-scoped.
Inferring the domain as celebrity information access, a single endpoint is severely incomplete. It likely provides only basic data without support for operations like searching by name, filtering by category, or updating information, leading to significant gaps that could hinder agent workflows.