Skip to main content
Glama
LinkupPlatform

mcp-search-linkup

by LinkupPlatform
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

67%
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. The tool 'search-web' has a clear, distinct purpose focused on web searching.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'search-web' follows a clear verb-noun pattern and is straightforward.

    Tool Count2/5

    A single tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and incomplete for a search-oriented server, lacking operations like filtering, advanced queries, or result management.

    Completeness2/5

    The server has a significant gap in its tool surface; it only provides search functionality without any way to refine, save, or manage results. For a search domain, this is incomplete and will likely cause agent failures in complex tasks.

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

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

  • This repository is archived. Archived repositories automatically receive an F maintenance tier.

  • 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

  • Behavior2/5

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

    No annotations are provided, so the description must fully disclose behavioral traits. It mentions that the search is 'in real time' and returns 'comprehensive content from the most relevant sources,' which adds some context. However, it lacks details on critical aspects like rate limits, authentication needs, error handling, or the format of returned content (e.g., links, summaries). For a tool with no annotations, this leaves significant gaps in behavioral understanding.

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

    Conciseness5/5

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

    The description is concise and well-structured, consisting of two sentences that efficiently convey the tool's purpose and usage guidelines without unnecessary details. Every sentence adds value: the first defines the action and context, and the second specifies when to use it and what it returns. There is no wasted verbiage, making it front-loaded and easy to parse.

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

    Completeness3/5

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

    Given the tool's complexity (a web search with two parameters) and the absence of annotations and output schema, the description provides a basic but incomplete picture. It covers the purpose and usage context adequately but lacks details on behavioral aspects like performance, limitations, or output format. For a tool with no structured output information, the description should ideally hint at return types or content structure to be more complete.

    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?

    The input schema has 100% description coverage, with clear documentation for both parameters (query and depth), including examples and enum values. The description does not add any parameter-specific information beyond what the schema provides, such as explaining how 'depth' affects search results in more detail. Given the high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate with additional semantic value.

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

    Purpose4/5

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

    The description clearly states the tool's purpose: 'Search the web in real time using Linkup' specifies the verb (search) and resource (web via Linkup). It further elaborates on the type of information retrieved ('trusted facts, news, or source-backed information'), making the purpose clear. However, since there are no sibling tools mentioned, it cannot differentiate from alternatives, preventing a score of 5.

    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?

    The description provides explicit guidance on when to use this tool: 'whenever the user needs trusted facts, news, or source-backed information.' This gives clear context for its application. However, it does not specify when not to use it or mention any alternatives, as there are no sibling tools, so it falls short of a perfect score.

    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

python-mcp-server MCP server

Copy to your README.md:

Score Badge

python-mcp-server 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/LinkupPlatform/python-mcp-server'

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