Use when the user names a GitHub login or selects one DevGlobe search result and needs its public profile and contribution evidence. No authentication is required. Example: {"login":"sajeetharan"}.
| Name | Required | Description | Default |
|---|---|---|---|
| login | Yes | GitHub login |
| Name | Required | Description | Default |
|---|---|---|---|
| profile | Yes | ||
| methodologyDisclaimer | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: no authentication is required and the data is public. This is meaningful for an agent deciding whether to invoke the 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 compact and front-loaded with the key usage condition. The example is brief and instructive, and no sentence is wasted.
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?
For a single-parameter read-only tool with a full output schema and comprehensive annotations, the description supplies all necessary invocation context: when to use it, what it returns at a high level, authentication requirements, and an example. Nothing essential is missing.
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?
The schema fully documents the only parameter, `login`, so the baseline is 3. The description adds value beyond the schema by providing a concrete JSON example and clarifying that the login comes from a user mention or a DevGlobe search selection.
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 identifies a clear verb-resource pair: retrieving a GitHub login's public profile and contribution evidence. It also distinguishes this from search-oriented siblings by tying usage to a specific login or a selected DevGlobe search result.
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 states when to use the tool: when the user names a GitHub login or selects a search result and wants profile/contribution information. It does not explicitly list when-not-to-use conditions or alternatives, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The discovery-oriented tools (search_developers, find_similar_developers, match_developers_to_repository, get_trending_developers) all return developers, but each is anchored to a distinct input—query, login, repository, or recency—so an agent can tell them apart. The remaining tools (profile, introduction status, contribution preview, request introduction) are clearly separated by action.
All tool names follow a consistent snake_case verb_noun pattern: search, find, get, match, preview, request. The noun clearly indicates the resource or action target, with no mixed casing or vague verbs.
Eight tools is a well-scoped surface for developer discovery and introduction. Each tool serves a distinct part of the workflow, and the count feels neither bloated nor thin.
The core workflow is covered: discovery, profile lookup, contribution preview, introduction request, and status check. A cancel or list introductions capability would round out the introduction lifecycle, but the essential agent journeys have no dead ends.
