Skip to main content
Glama
Camcdonou

syn-search-mcp

by Camcdonou
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Server Quality Checklist

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

  • Latest release: v1.0.0

  • Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clear and unambiguous.

    Naming Consistency5/5

    The tool name 'synthetic_search' follows a clear snake_case verb_noun pattern, which is consistent and descriptive.

    Tool Count4/5

    With a single tool, the server is minimal but well-scoped for a dedicated search service. While typical counts range 3-15, this is acceptable for a single-purpose API.

    Completeness5/5

    The tool covers the full search workflow, including configurable detail levels (summary vs. full text) and output truncation handling, making it comprehensive for its stated domain.

  • Average 4.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
    • 1 commit 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

  • Behavior4/5

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

    Annotations already declare readOnlyHint=true and openWorldHint=true, which the description is consistent with. It adds valuable behavioral context beyond the annotations: the output truncation limit (2000 lines or 50KB), the temp-file fallback when exceeded, and the result format. This is useful operational detail.

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

    Conciseness4/5

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

    Four sentences with no filler; the core purpose is front-loaded before usage guidance and truncation caveats. Each sentence contributes distinct information without redundancy. Appropriately sized for the tool's complexity.

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

    Completeness4/5

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

    With no output schema, the description correctly carries the burden of explaining return values (titles, URLs, snippets), which it does. It also covers detail_level guidance and truncation behavior. Minor gap: no explicit mention of max_results defaults, but that is covered by the schema. Fairly complete for a search 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 coverage is 100%, so the schema fully documents all four parameters with descriptions. The description adds modest usage nuance (recommending ai-summary for real questions, noting summary_prompt focuses the summarizer) but largely reinforces what the schema already states. Baseline 3 is appropriate given the schema does the heavy lifting.

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

    Purpose5/5

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

    States a specific verb and resource ('Search the web via Synthetic's Search API') and describes the output format (titles, URLs, text snippets). The purpose is unambiguous and complete. No siblings exist to differentiate from, but the core purpose is fully specified.

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

    Usage Guidelines4/5

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

    Provides explicit internal usage guidance: recommends detail_level='ai-summary' for real questions, 'full' for complete text, and explains when summary_prompt should be supplied. Since no sibling tools are listed, it cannot name alternatives, but the in-tool routing guidance is clear and actionable.

    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

syn-search-mcp MCP server – quality and maintenance score on Glama

Copy to your README.md:

Score Badge

syn-search-mcp MCP server – quality and maintenance score on Glama

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/Camcdonou/syn-search-mcp'

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