Skip to main content
Glama

Develust

by com.develust.ai
OverviewDiscussionsAdmin

search

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe input query.
ai_search_optionsNoOptions for customizing the AI search behavior.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ai_search_options / properties / custom_metadata
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • changedInput schema / properties / ai_search_options / properties / retrieval / properties / filters / additionalProperties / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "number"
-      },
-      {
-        "type": "boolean"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  {
-    "properties": {
-      "$eq": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "$gt": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          }
-        ]
-      },
-      "$gte": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          }
-        ]
-      },
-      "$in": {
-        "items": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "number"
-            },
-            {
-              "type": "boolean"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "type": "array"
-      },
-      "$lt": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          }
-        ]
-      },
-      "$lte": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          }
-        ]
-      },
-      "$ne": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "$nin": {
-        "items": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "number"
-            },
-            {
-              "type": "boolean"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "type": "array"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": [
+      "string",
+      "number",
+      "boolean",
+      "null"
+    ]
+  },
+  {
+    "properties": {
+      "$eq": {
+        "type": [
+          "string",
+          "number",
+          "boolean",
+          "null"
+        ]
+      },
+      "$gt": {
+        "type": [
+          "string",
+          "number"
+        ]
+      },
+      "$gte": {
+        "type": [
+          "string",
+          "number"
+        ]
+      },
+      "$in": {
+        "items": {
+          "type": [
+            "string",
+            "number",
+            "boolean",
+            "null"
+          ]
+        },
+        "type": "array"
+      },
+      "$lt": {
+        "type": [
+          "string",
+          "number"
+        ]
+      },
+      "$lte": {
+        "type": [
+          "string",
+          "number"
+        ]
+      },
+      "$ne": {
+        "type": [
+          "string",
+          "number",
+          "boolean",
+          "null"
+        ]
+      },
+      "$nin": {
+        "items": {
+          "type": [
+            "string",
+            "number",
+            "boolean",
+            "null"
+          ]
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  }
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / ai_search_options / properties / query_rewrite / properties / enabled / const
      Added value: +false
    • removedInput schema / properties / ai_search_options / properties / query_rewrite / properties / model
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / ai_search_options / properties / reranking / properties / enabled / const
      Added value: +false
    • removedInput schema / properties / ai_search_options / properties / reranking / properties / model
      Removed value: -{
-  "type": "string"
-}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description characterizes the tool as 'authoritative information' but does not disclose behavioral details such as return format, whether it performs live retrieval, or how results are ranked. Although there are no annotations to contradict, the description carries the burden and provides minimal transparency beyond its subject scope.

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 a concise two-sentence definition with the core purpose front-loaded and a usage directive at the end. It earns its place without redundant explanation, though it could be improved in minimal space.

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?

For a simple search tool with one required parameter and no output schema or annotations, the description adequately defines scope but leaves unstated expected result behavior and limits. As a basic information-retrieval tool it is likely sufficient, but completeness is only moderate.

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 coverage is 100%, so the required 'query' parameter is already documented by the schema. The description does not add meaning beyond saying to search, but it contextualizes what kinds of queries are relevant. This meets the baseline for a high-coverage 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?

States a specific verb ('search'), a concrete resource (Develust Technology's software/web development services), and explicitly lists what information it covers (expertise, offerings, capabilities, engagement). The scope is precise and an agent can determine when to invoke it without ambiguity.

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?

Explicitly instructs to use this tool for any question about Develust's expertise, service offerings, project capabilities, or engagement. It lacks explicit exclusions or named alternatives, but the use-case guidance is strong and sufficient for a tool with no siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Develust toolsInspect
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.

Resources