search-boost-mcp

by Mr-remon219

Overview Schema Related Servers Score Discussions

JavaScript

Local

Server Quality Checklist

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

Latest release: v0.1.6
Disambiguation5/5
Each tool has a clear, distinct purpose: fetch_page extracts text from URLs, fused_search performs general web search, search_layer manages API layer configuration, deep_research runs multi-step research, x_search targets Twitter-specific queries, and search_stats provides diagnostics. No two tools overlap in intent, making selection unambiguous.
Naming Consistency4/5
All names use lowercase snake_case and follow a pattern of modifier+noun (e.g., fused_search, deep_research, x_search, search_stats), though fetch_page uniquely uses a verb+noun structure. This minor deviation is easily readable and does not create confusion.
Tool Count5/5
With 6 tools, the set is well-scoped for a search/boost utility. Each tool contributes to distinct functional areas: fetching, multi-engine search, configuration, deep research, social search, and diagnostics, justifying its inclusion without bloating the surface.
Completeness4/5
The tool surface covers the full search lifecycle: input (fused_search, x_search), processing (deep_research includes analysis and follow-ups), content access (fetch_page), configuration (search_layer), and observability (search_stats). Minor omissions like image search or trend analysis are not critical for the core domain.
Average 4/5 across 6 of 6 tools scored. Lowest: 3.1/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 49 commits in the last 12 weeks
- Last stable release on August 18, 2026
- 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

Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable context: it works without credentials (multi-engine + oEmbed fallback) and mentions the official API path. This goes beyond what annotations provide, though it could detail fallback behavior more.
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?
The description is two sentences, front-loaded with the main capability. It is concise without wasted words, but could be slightly more structured (e.g., separating search types from credential notes).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the description does not explain how different search types require specific parameters (e.g., thread needs post_id, user needs username). It lacks completeness for a tool with 7 parameters and multiple search modes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 29% (only to_date and from_date have descriptions). The description does not explain any parameters, such as how query, post_id, username, or max_results relate to the search types. Given low coverage, the description should compensate but does not.
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 performs real-time X/Twitter search with four specific types: keyword, semantic, user profile, or thread. It also mentions credential modes. However, it does not explicitly differentiate from sibling tools like fused_search or search_layer, which could be helpful for selection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions that the tool works without credentials but has an official path via grok login or XAI_API_KEY. This provides some context on authentication, but it does not give any guidance on when to use this tool versus sibling tools or what prerequisites are needed for each search type.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context: use of Jina Reader with a local HTML fallback (indicating reliability strategy) and focus filtering for token savings. No contradictions.
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?
Two sentences: first states the core function and method, second adds the optional focus feature. No redundant or wasted content. Front-loaded effectively.
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?
Given low complexity (2 params), rich schema descriptions, annotations, and an output schema, the description covers the main behavior and the focus filter. It could mention error handling or timeout but is sufficient for a simple fetch 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 description coverage is 100%, with both parameters already well-described ('http(s) URL to fetch', 'Keep paragraphs matching these terms (~90% token savings)'). The description only echoes 'Use focus to filter paragraphs', adding no new meaning.
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?
The description states 'Fetch readable page text via Jina Reader with local HTML fallback', which is a specific verb+resource. It distinguishes from sibling search tools (e.g., fused_search, deep_research) by targeting a single URL rather than performing searches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternatives are provided. However, the description implies usage for fetching content from a specific URL, and sibling tool names (search tools) suggest the context. Guidance is implied but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate readOnly/openWorld/not destructive, and the description adds meaningful behavioral context: the tool is one round of an iterative workflow, returns gaps with suggested follow-up queries, and should be concatenated into a cited synthesis. This gives the agent useful expectations beyond the annotation flags.
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 two sentences, front-loaded with the core capability, and contains no filler. The iterative call pattern and final synthesis are stated economically and clearly.
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?
The description captures the essential workflow: perform one research round, follow the suggested follow-ups, stop when gaps are empty, then synthesize with citations. Since an output schema exists, return-value detail is not required. The main gap is the poor explanation of the parameter semantics, but overall the high-level usage context is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is very low (17%), so the description must compensate, but it only vaguely refers to 'suggested_queries' without explicitly mapping it to the 'queries' parameter. The meaning of 'layer', 'recency', 'round', and 'max_sources' is left entirely to the schema, which is insufficient given the low coverage.
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?
The description clearly states it performs 'one research round' combining 'complex fused search + coverage analysis + gaps + suggested follow-up queries.' This is a specific multi-phase verb-resource description that also distinguishes the tool from sibling tools like fetch_page and x_search by emphasizing iterative research coverage.
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?
It gives explicit usage guidance: 'Call repeatedly with suggested_queries until gaps is empty, then synthesize with citations.' This clearly explains the iteration and termination conditions. However, it does not explicitly compare against sibling tools or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the behavioral profile is clear. The description adds useful context about what diagnostics are included but does not mention rate limits, permissions, or other traits beyond the annotations.
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 a single, concise line with no wasted words. It is front-loaded with 'Diagnostics:' to immediately signal purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, an output schema, and clear sibling tool names (all search functions), the description is complete for an agent to understand the tool's purpose and when to use it.
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?
There are zero parameters, so baseline is 4. The description adds value by listing the diagnostic categories, which is the only source of information about what the tool returns.
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?
The description clearly indicates this is a diagnostics tool for search statistics, listing specific categories (cache hits/misses, tier counts, etc.). It distinguishes itself from sibling tools like fused_search and deep_research, which are search functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly suggests use for diagnostics, but does not explicitly state when to use this tool versus alternatives (e.g., 'use this to check cache health, not for searching'). No exclusion criteria or sibling differentiation is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only behavior (readOnlyHint: true). The description adds context about URL dedupe, cross-ranking, and key requirements, which are behaviors not fully covered by annotations. This enriches transparency beyond the annotation baseline.
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 exceptionally concise—two sentences—and well-structured. It avoids redundancy and directly conveys essential information without extraneous words, making it easy to parse.
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?
Given the schema provides some parameter descriptions and an output schema is present, the description's lack of return format or further behavioral details is acceptable. It supplies sufficient context for a search tool, but could be slightly more thorough regarding result handling or limitations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not explain any parameter semantics. Schema coverage is only 44% (query and max_results have descriptions), leaving many parameters (layer, engines, queries, recency, complexity, exclude_domains, include_domains) undocumented. Since the description adds no parameter details, it fails to compensate for incomplete schema.
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?
The description clearly states the tool's function: 'Multi-engine parallel search with URL dedupe and cross-ranking.' It specifies the action (search), the resource (multi-engine), and distinguishes from a built-in WebSearch, meeting the bar for specificity and differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit guidance on when to use this tool: 'Prefer over built-in WebSearch for version-sensitive facts, APIs, comparisons, and research.' It also differentiates free vs. API layers, offering clear usage context without ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate this is not read-only and not destructive; the description adds meaningful context by explaining what switching to 'free' vs 'api' changes about the underlying engine composition. It does not detail side effects or persistence, but for a simple configuration switch, the disclosed behavior is sufficient. No contradiction with annotations.
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 extremely compact, with the core action front-loaded in the first sentence and the mode meanings packed into the second. Every clause adds value, and there is no redundant repetition of the title or schema.
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?
For a one-parameter optional configuration tool with no output schema, the description covers the main decision space well. The only notable gap is 'show' behavior not being described in the mode definitions, but the overall tool is simple enough that this does not severely compromise completeness.
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?
With 0% schema description coverage, the description carries the burden of explaining parameters. It successfully explains two of the three enum values ('free' and 'api') with concrete engine lists. The 'show' value is only implied by the opening verb and lacks explicit detail about what it displays or returns.
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?
The description opens with a specific verb+resource combination, 'Switch or show search layer,' which clearly identifies the action and target. It also distinguishes this tool from the sibling search tools by focusing on layer configuration rather than executing searches, and the mode definitions reinforce the purpose.
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 gives clear context for when to choose each layer value: 'free' for keyless engines only, 'api' for adding keyed engines, and 'show' to inspect the current layer. It does not explicitly state when not to use the tool or name alternatives, but the mode explanations provide practical selection guidance.
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

Copy to your README.md:

[![search-boost-mcp MCP server — quality and maintenance score on Glama](https://glama.ai/mcp/servers/Mr-remon219/search-boost/badges/card.svg)](https://glama.ai/mcp/servers/Mr-remon219/search-boost)

Score Badge

Copy to your README.md:

[![search-boost-mcp MCP server — quality and maintenance score on Glama](https://glama.ai/mcp/servers/Mr-remon219/search-boost/badges/score.svg)](https://glama.ai/mcp/servers/Mr-remon219/search-boost)

shields.io Endpoint

For READMEs with an existing badge row. Append &style=flat-square (or any other shields.io style) to match the rest, and &metric=tools, &metric=maintenance or &metric=claim to badge a different dimension.

[![search-boost-mcp MCP server — quality and maintenance score on Glama](https://img.shields.io/endpoint?url=https%3A%2F%2Fglama.ai%2Fmcp%2Fservers%2FMr-remon219%2Fsearch-boost%2Fbadges%2Fshields.json)](https://glama.ai/mcp/servers/Mr-remon219/search-boost)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/Mr-remon219/search-boost'

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