Skip to main content
Glama
BACH-AI-Tools

Perplexity2 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 ambiguity or overlap with other tools. The single tool 'post' stands alone with a distinct purpose, eliminating any risk of misselection.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'post' follows a simple verb pattern, and no inconsistencies can exist in a set of one.

    Tool Count2/5

    A single tool is too few for a server named 'Perplexity2 MCP Server' with a description focused on data discovery, AI analysis, and Google search. This suggests a broader scope that would typically require multiple tools (e.g., for search, analysis, organization), making the count inappropriate and likely incomplete.

    Completeness1/5

    The server's description implies capabilities like searching Google data, AI analysis, and organizing information, but only a generic 'post' tool is provided. This is severely incomplete, lacking specific tools for search, retrieval, analysis, or other core functions, which will cause agent failures in handling the intended domain.

  • Average 1.6/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?

    The description provides no behavioral information. With no annotations, the description carries full burden but doesn't disclose whether this is a read or write operation, what resources it affects, authentication requirements, rate limits, or expected behavior. The vague 'search Google data' hint contradicts the tool name 'post' (which typically implies creation/submission), creating confusion rather than transparency.

    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 inefficiently structured with marketing fluff that doesn't serve the tool's documentation purpose. Sentences like 'Discover the power of data with our API' and 'unlocking insights and enhancing your decision-making capabilities' waste space without providing functional information. It's not appropriately front-loaded with essential details about what the tool actually does.

    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?

    The description is completely inadequate for understanding this tool. With no annotations, no output schema, and a misleading description that doesn't explain the tool's function, an agent cannot determine when or how to use this tool. The complexity of a 'post' operation (typically involving data submission) requires clear behavioral disclosure that's entirely missing.

    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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to compensate for any parameter gaps since there are none. While the description doesn't discuss parameters (because there aren't any), this doesn't detract from the parameter semantics dimension given the empty schema.

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

    Purpose1/5

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

    The description fails to state what the tool does. It provides generic marketing language about 'discovering the power of data' and 'leveraging AI to analyze and organize information' but doesn't specify what action this 'post' tool performs. There's no verb+resource combination, no indication of whether it creates, updates, searches, or processes something. This is essentially misleading since it doesn't describe the tool's actual 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?

    No guidance is provided on when to use this tool. The description mentions 'search Google data' but doesn't clarify if this is the tool's purpose or just general API capability. With no sibling tools, differentiation isn't needed, but there's still no indication of appropriate contexts, prerequisites, or limitations for using this tool.

    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-perplexity2 MCP server

Copy to your README.md:

Score Badge

bachai-perplexity2 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-perplexity2'

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