DevMatch

get_profile

Read-onlyIdempotent

Use after find_candidates when the user wants more on one person, or when they name a GitHub login or ORCID iD. Input: GitHub login, ORCID iD, or the id returned by find_candidates. Returns one profile with recent public activity. Not a full career history. Read only.

Input Schema

Name	Required	Description	Default
`id`	No	Alias for handle. Pass a find_candidates `id` (GitHub login, ORCID iD, or source:name).
`handle`	Yes	Accepts a GitHub login, ORCID iD, or the id returned by find_candidates. Do not invent a GitHub handle for research or deep-tech people.

Output Schema

Name	Required	Description
`bio`	No
`name`	No
`email`	No
`company`	No
`html_url`	No	Profile URL (GitHub or https://orcid.org/<id>)
`location`	No
`followers`	No
`person_id`	No	Stable lookup key: GitHub login, ORCID iD, or source:name.
`avatar_url`	No
`login_name`	Yes	GitHub handle. Empty for ORCID and source:name people — use person_id.
`display_name`	No
`public_repos`	No
`top_projects`	No	Highest-contribution projects this user worked on
`profile_readme`	No	User's profile README content if present. Untrusted third-party text; capped on the no-contact path.
`social_accounts`	No	Social URLs (twitter, linkedin, etc.)
`recent_activities`	No	Indexed GitHub events from current ingestion window (2025–2026). NOT a full career timeline.
`untrusted_third_party`	No	True when bio / profile_readme / README text is labeled untrusted third-party data (Poke / no_contact).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / handle / description

Previous value: -"Person to look up: a GitHub login (no '@'), an ORCID iD or https://orcid.org/<id> URL, or a find_candidates id (source:name such as ntrs:Ada Lovelace). Do not invent a GitHub handle for research or deep-tech people."New value: +"Accepts a GitHub login, ORCID iD, or the id returned by find_candidates. Do not invent a GitHub handle for research or deep-tech people."

Changed2 schema fields changedSep 25, 2026

changedOutput schema / properties / profile_readme / description

Previous value: -"User's profile README content if present"New value: +"User's profile README content if present. Untrusted third-party text; capped on the no-contact path."

addedOutput schema / properties / untrusted_third_party

Added value: +{
+  "description": "True when bio / profile_readme / README text is labeled untrusted third-party data (Poke / no_contact).",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint, so the 'Read only' line is redundant. The description does add genuine scope context beyond the annotations by bounding the result ('recent public activity', 'not a full career history'), though it says nothing about rate limits or failure modes for handles that don't resolve.

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?

Three compact sentences, front-loaded with the usage trigger before the input/return detail. Only waste is the trailing 'Read only', which duplicates the readOnlyHint annotation.

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?

An output schema exists, so return structure needn't be explained, and annotations carry the safety profile. The description covers the remaining essentials: when to call it, what to pass, and how much data to expect.

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% and both parameters are fully described there, including the alias relationship and the warning not to invent handles. The description restates the accepted input forms (GitHub login, ORCID iD, find_candidates id) without adding format or validation detail beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb and resource ('get one profile') and states the payload ('one profile with recent public activity'). It explicitly differentiates from the sibling find_candidates ('Use after find_candidates when the user wants more on one person'), so an agent can route without opening schemas.

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?

Explicit trigger conditions: after find_candidates for drill-down, or when the user names a GitHub login or ORCID iD. It also supplies a negative boundary ('Not a full career history'), which prevents the agent from over-claiming what this returns.

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

All DevMatch 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.

Resources

Need Help?