Skip to main content
Glama
BACH-AI-Tools

Celebrity By Api Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

  • Average 1.7/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior1/5

    Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

    No annotations are provided, so the description carries full burden for behavioral disclosure. The description reveals nothing about how the tool behaves - no information about whether it's a read or write operation, what authentication is required, rate limits, error behavior, or what kind of data it returns. For a tool with 6 parameters and no annotations, this represents a complete failure to disclose behavioral traits.

    Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

    Conciseness2/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    While technically concise (only 5 words), this is under-specification rather than effective conciseness. The single sentence fails to convey essential information about the tool's purpose and usage. Every sentence should earn its place, but this sentence provides almost no value beyond what's already in the tool name.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness1/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    Given a tool with 6 parameters, no annotations, and no output schema, the description is completely inadequate. It fails to explain what the tool does, how to use it, what it returns, or any behavioral characteristics. The description doesn't compensate for the lack of structured metadata, leaving the agent with insufficient information to effectively use this tool.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters3/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds zero additional information about parameters - it doesn't explain relationships between parameters, provide examples of combined usage, or clarify the overall search logic. With complete schema coverage, the baseline is 3 even without parameter information in the description.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose2/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description 'API Ninjas Celebrity API endpoint' is tautological - it restates the tool name 'v1celebrity' without explaining what it actually does. It mentions 'Celebrity API' but doesn't specify the action (search, retrieve, list, etc.) or what resource it operates on beyond the generic 'endpoint' reference. There's no clear verb+resource combination that defines the tool's function.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines1/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description provides absolutely no guidance on when to use this tool. There's no mention of use cases, prerequisites, or alternative approaches. With no sibling tools mentioned, the bar is lower, but the description fails to give any context about appropriate usage scenarios or limitations.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

celebrity_by_api_ninjas MCP server

Copy to your README.md:

Score Badge

celebrity_by_api_ninjas MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/celebrity_by_api_ninjas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server