A
licenseNot graded
qualityB
maintenancePerplexity for social: ask what competitors are running across social and get answers grounded in real ad and creative data, not guesses.
2
Apache 2.0
MCP Tool Response Reference
by 91.174.133.8
Server Details
Searches the web using DuckDuckGo and returns relevant result titles, URLs, and snippets for a given query. Supports limiting the number of results.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
B3/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool in the set, there is no possibility of an agent confusing it with another tool. Its purpose (web search) is unambiguous by construction.
Naming Consistency4/5
The lone name 'search_query_v1' uses snake_case, which is readable and predictable. The appended '_v1' version suffix is an unusual convention, but with one tool there is no cross-tool inconsistency to assess.
Tool Count2/5
A server offering only one tool is very thin for any stated scope, and the server name ('MCP Tool Response Reference') implies a broader reference surface than a single search operation. One tool rarely earns its place as a complete server.
Completeness2/5
The surface provides search but no follow-up operations such as fetching a result's content, pagination, or any other reference/lookup capability hinted at by the server name. Agents hit a dead end after receiving results.
Available Tools
1 toolsearch_query_v1CInspect
Search DuckDuckGo and return formatted results.
Args:
query: The search query string
max_results: Maximum number of results to return (default: 10)
ctx: MCP context for logging
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| max_results | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the search provider (DuckDuckGo) and that results are formatted, which is useful, but says nothing about rate limits, result ranking/freshness, failure modes, or whether requests are cached or logged.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The opening sentence is well front-loaded, but the remaining content is a verbatim docstring "Args:" block, including an undocumented `ctx` entry. It is short, yet part of its length is boilerplate rather than information that helps an agent invoke the tool.
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?
The tool is simple (one required param, output schema present so return format need not be described), and the description covers the provider and result formatting. However, for a network-dependent search tool it omits rate limits, error behavior, and any guidance on choosing max_results, leaving modest gaps.
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 0%, so the description does document both parameters, but its text ("The search query string", "Maximum number of results to return") merely restates the schema property titles, and the default of 10 is already in the schema. It also references a `ctx` parameter that does not exist in the input schema, which adds confusion rather than meaning.
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?
States a concrete verb (search) plus the specific resource (DuckDuckGo) and what it produces (formatted results), so an agent can tell instantly what it does. It only lacks sibling differentiation, but no sibling tools exist here.
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?
There is no indication of when to use this tool versus alternatives (e.g., other search sources or fetch tools), nor any preconditions such as network access or query constraints. Usage must be inferred entirely from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
search_query_v1
Related MCP Servers
- AlicenseCqualityBmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs119 npmMIT
- AlicenseAqualityCmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT
industrylens-mcpofficial
AlicenseNot gradedqualityBmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.