DevGlobe

search_developers

Read-onlyIdempotent

Use when the user wants to find public developers by skill, name, language, location, agent availability, or active opportunity intent. Start discovery here; no authentication is required. Example: {"query":"TypeScript maintainers","location":"Germany","availableForAgents":true,"limit":5}.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results from 1 to 20
`query`	Yes	Required natural-language public search intent, such as "TypeScript maintainers" or a developer name
`language`	No	Optional primary programming language, such as "TypeScript"
`location`	No	Optional public location text, such as "Germany" or "Colombo"
`opportunityType`	No	Optional active self-declared opportunity type; do not infer availability
`availableForAgents`	No	Set true only when the user needs profiles accepting verified agent requests

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`resultCount`	Yes
`methodologyDisclaimer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

addedOutput schema / properties / results / items / properties / match

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "disclaimer": {
+      "type": "string"
+    },
+    "label": {
+      "enum": [
+        "Strong match",
+        "Good match",
+        "Related match"
+      ],
+      "type": "string"
+    },
+    "method": {
+      "enum": [
+        "text",
+        "semantic",
+        "hybrid"
+      ],
+      "type": "string"
+    },
+    "reasons": {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 3,
+      "type": "array"
+    },
+    "score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "signals": {
+      "items": {
+        "enum": [
+          "text",
+          "semantic"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "score",
+    "label",
+    "reasons",
+    "signals",
+    "method",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A5/5.0

Behavior5/5

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

The description is consistent with the annotations (readOnly, idempotent, openWorld). It adds behavioral details such as 'no authentication required' and warns 'do not infer availability' for opportunityType. No side effects or destructive actions are implied, and the read-only nature is transparent.

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 compact and efficient, combining purpose, usage trigger, authentication note, and an example in just a few sentences. There is no redundant or extraneous content, and the example is well-placed to illustrate the tool's use.

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 the tool's simplicity and the presence of a full input schema, the description provides all necessary context: what it does, when to use it, and a concrete example. The output schema is indicated as existing but not required to be explained in the description, and the tool's role within the sibling set is clarified by 'Start discovery here.'

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All six parameters are fully described in the schema, and the example in the description demonstrates how to use them (e.g., query, location, availableForAgents). The description also clarifies conditional usage like 'Set true only when the user needs profiles accepting verified agent requests,' which adds semantic value beyond the raw 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 purpose: 'find public developers by skill, name, language, location, agent availability, or active opportunity intent.' It uses a specific verb ('find') and resource ('developers'), and the phrase 'Start discovery here' indicates its role as a primary search tool, distinguishing it from sibling tools like find_similar_developers or get_developer_profile.

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?

The description explicitly says 'Use when the user wants to find public developers...' and provides a concrete example. It also notes 'Start discovery here' and 'no authentication is required,' which are clear usage guidelines. This leaves no ambiguity about when to invoke this tool.

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

All DevGlobe tools Inspect

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.