pixserp
Server Details
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- TetiAI/pixserp-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent; 'search' is a clear verb that matches the tool's purpose.
One tool for a server that claims to cover 10 answer shapes feels thin; a single monolithic tool lacks granularity and may limit agent flexibility.
The tool description indicates it covers 10 answer shapes automatically, suggesting broad coverage for web search needs; however, there may be gaps for specialized operations or manual selection.
Available Tools
1 toolsearchAInspect
Search the live web and get an AI-synthesized answer with structured citations. One endpoint covers 10 answer shapes — web, news, images, places & maps, shopping, flights, hotels, YouTube, transcripts, any URL — the right one is picked automatically from your query. Use this whenever you need fresh, factual information from the web.
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | `pixserp-fast` = quick single-search lookup (default). `pixserp-standard` = balanced. `pixserp-deep` = multi-angle thorough research. `pixserp-agent` = multi-step research loop, decides itself when to stop. | pixserp-fast |
| query | Yes | What to search for. Phrase as a natural-language question or a specific topic. | |
| max_steps | No | Only used when `model = pixserp-agent`. Caps the research loop length. Default 50, max 100. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions that the tool returns an 'AI-synthesized answer' and that the answer shape is automatically selected. However, it does not disclose error behavior, rate limits, authentication requirements, or any constraints. The description is adequate but lacks depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: one sentence stating purpose, one listing capabilities, and one giving usage guidance. Every sentence adds value with no redundancy. It is front-loaded with the core purpose, making it easy for an agent to quickly understand.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (10 answer shapes, multiple model options), the description covers key aspects: what it does, when to use, and the auto-selection behavior. It mentions 'structured citations' but does not detail the output format. Since there is no output schema, a bit more detail on the response structure would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with each parameter having a clear description. The tool description reinforces that the query should be a 'natural-language question' but does not add significant meaning beyond the schema. The baseline of 3 is appropriate as the schema already provides sufficient detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Search the live web and get an AI-synthesized answer with structured citations', specifying the verb 'search' and resource 'live web'. It enumerates 10 answer shapes, making the purpose specific and comprehensive. No sibling tools exist to differentiate, but the description is self-contained and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises 'Use this whenever you need fresh, factual information from the web', providing clear usage context. It does not specify when not to use the tool or mention alternatives, but given there are no sibling tools, this is acceptable. The guidance is sufficient for an agent to decide when to invoke.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!