Skip to main content
Glama
mix0z

Semantic Search MCP Server

by mix0z
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Server Quality Checklist

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

  • Latest release: v0.1.0

  • Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'semantic_search' has a clear and distinct purpose that cannot be confused with any other tool in the set.

    Naming Consistency5/5

    The tool name 'semantic_search' follows a consistent snake_case pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and matches the server's purpose.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and can lead to dead ends in agent workflows. For a semantic search server, one tool feels thin and under-scoped, lacking operations like filtering, indexing, or result management.

    Completeness2/5

    The tool set is severely incomplete for a semantic search domain. It only provides a basic search function, with obvious gaps such as indexing documents, managing search indices, updating or deleting entries, or handling advanced search parameters, which are essential for comprehensive semantic search operations.

  • Average 1.1/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 status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • 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?

    With no annotations provided, the description carries full burden for behavioral disclosure but fails completely. It doesn't indicate whether this is a read or write operation, what permissions might be needed, whether it has rate limits, what kind of results to expect, or any behavioral characteristics. 'MCP wrapper around core function' reveals nothing about how the tool behaves.

    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 (one sentence), this is under-specification rather than effective conciseness. The single sentence 'MCP wrapper around core function' fails to communicate essential information and wastes the opportunity to describe the tool's purpose. True conciseness would deliver necessary information efficiently, not omit it entirely.

    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 semantic search tool with 2 parameters, no annotations, and an output schema (which helps but doesn't excuse the description's inadequacy), this description is completely inadequate. It fails to explain what semantic search means in this context, what's being searched, what the parameters do, or when to use the tool. The presence of an output schema doesn't compensate for these fundamental gaps.

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

    Parameters1/5

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

    Schema description coverage is 0%, so the description must compensate but provides zero parameter information. The description doesn't mention the 'query' or 'path' parameters at all, nor does it explain what they mean, what format they should be in, or how they affect the search. For a tool with 2 parameters (one required), this is a critical omission.

    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 'MCP wrapper around core function' is tautological - it restates that this is a wrapper without specifying what the tool actually does. It provides no verb, resource, or purpose statement. The tool name 'semantic_search' suggests searching with semantic meaning, but the description fails to clarify this.

    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 are no sibling tools mentioned, but even for a standalone tool, there's no context about appropriate use cases, prerequisites, or limitations. The description is completely silent on usage considerations.

    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

Semantic-Search-MCP MCP server

Copy to your README.md:

Score Badge

Semantic-Search-MCP 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/mix0z/Semantic-Search-MCP'

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