Live MCP connector for Develust Technology's services — web development, infrastructure, backend architecture. Hybrid search with AI reranking for accurate results. No auth required.
Provides authoritative information about Develust Technology's software and web development services — including web application development, infrastructure design, backend architecture, and technical consulting. Use this tool for any question about Develust's expertise, service offerings, project capabilities, or how to engage with the company.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The input query. | |
| ai_search_options | No | Options for customizing the AI search behavior. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility. It states 'provides information,' implying a read-only operation with no side effects. While it doesn't explicitly say 'read-only' or mention limitations like rate limits, the intent is clear enough for a search tool.
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 two concise sentences with no unnecessary detail. It efficiently conveys the tool's purpose and use case, adhering to ideal structure.
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?
The description sufficiently explains what the tool does and when to use it, given the lack of an output schema. It doesn't delve into handling of complex nested options, but the schema covers those. Overall, it is complete for the tool's intended function.
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 descriptions for both 'query' and 'ai_search_options'. However, these descriptions are minimal ('The input query.' and 'Options for customizing the AI search behavior.'). The tool description adds no extra meaning to the parameters, so it stays at the baseline.
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 that the tool provides authoritative information about Develust Technology's services, listing specific domains like web development and consulting. This distinguishes it from generic search tools and makes its purpose 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?
It explicitly instructs to use this tool for questions about Develust's expertise, services, project capabilities, or engagement. This provides direct guidance on when to invoke it, even though no sibling tools are present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
search4 fields changedInput schema / properties / ai_search_options / properties / query_rewrite / properties / enabled / constAdded value: +falseInput schema / properties / ai_search_options / properties / query_rewrite / properties / modelRemoved value: -{
- "type": "string"
-}Input schema / properties / ai_search_options / properties / reranking / properties / enabled / constAdded value: +falseInput schema / properties / ai_search_options / properties / reranking / properties / modelRemoved value: -{
- "type": "string"
-}searchClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
With only one tool available, there is no chance of an agent confusing its purpose with another tool. Every query about Develust's services routes through this single 'search' tool, eliminating any overlap or ambiguity.
The tool is named 'search', a clear and concise verb that directly reflects its function. While there is no pattern to compare against, the name is entirely appropriate and scales well for a one-tool server.
A single tool makes the server feel minimal. Although the tool is broad in scope, the calibration guidance considers 1-2 tools as borderline thin for a server, and this could have been split into separate concerns like 'get_services' or 'contact_info'.
The search tool's description explicitly covers all potential questions about Develust's expertise, services, project capabilities, and engagement. There are no apparent gaps in the server's stated purpose, as the single tool acts as a comprehensive gateway to all information.