Skip to main content
Glama
BACH-AI-Tools

Pan Card Verification At Lowest Price MCP Server

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 confusion or overlap between tools. The single tool 'pan_verify' has a clear and distinct purpose for PAN card verification.

    Naming Consistency5/5

    The naming follows a consistent snake_case pattern with a verb-noun structure ('pan_verify'). Since there is only one tool, it inherently maintains perfect consistency without any deviations.

    Tool Count2/5

    A single tool is too few for a server that implies a broader scope like 'Pan Card Verification At Lowest Price,' which might suggest additional functionalities such as status checks, pricing queries, or batch processing. This minimal set feels thin and incomplete for the apparent domain.

    Completeness2/5

    The tool set is severely incomplete for the server's purpose. While 'pan_verify' covers verification, there are obvious gaps such as checking verification status, retrieving pricing information, handling multiple PANs, or managing verification history, which are typical in such services.

  • Average 1.8/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 the full burden of behavioral disclosure. 'verify pan' offers no information about what the tool does operationally—whether it's a read-only check, requires authentication, has side effects, returns specific data, or handles errors. It fails to describe any behavioral traits beyond the minimal action implied by the name.

    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?

    The description is extremely brief ('verify pan'), which is concise but under-specified rather than efficiently informative. It lacks structure and fails to front-load essential details, making it more of a placeholder than a helpful description. Conciseness should not come at the cost of clarity, which is lacking here.

    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 the tool's name and lack of annotations, output schema, or sibling tools, the description is incomplete. It does not explain what 'pan' is, what verification involves, what the expected output might be, or any operational context. For a tool with no structured data to rely on, this description fails to provide the necessary completeness for effective agent use.

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

    Parameters4/5

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

    The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter details, but since there are no parameters, this is acceptable. The baseline score for 0 parameters is 4, as the description need not compensate for missing parameter information.

    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 'verify pan' is a tautology that essentially restates the tool name without providing meaningful context about what 'pan' refers to or what verification entails. It lacks a specific verb+resource combination and doesn't distinguish from any siblings (though none exist). While it minimally indicates the tool's function, it remains vague and uninformative.

    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 no guidance on when to use this tool, what context it applies to, or any prerequisites or alternatives. There is no mention of scenarios, conditions, or comparisons to other tools, leaving the agent with no usage direction beyond the tool name.

    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

bachai-pan-card-verification-at-lowest-price MCP server

Copy to your README.md:

Score Badge

bachai-pan-card-verification-at-lowest-price 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/bachai-pan-card-verification-at-lowest-price'

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