DevMatch

get_profile

Read-onlyIdempotent

Fetch one contributor's profile card by GitHub login, ORCID iD (or orcid.org 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 — pass their id. find_candidates already returns full inline profiles; use get_profile only for ids outside those results or when the user asks for deeper detail.

Returns structuredContent (view=profile). Agents: consume structuredContent only.

IMPORTANT — interpreting recent_activities: indexed GitHub activity in the current ingestion window (2025–2026), up to ~20 events per recent project. NOT a complete career history. Empty or older activity does not mean inactive.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Alias for handle. Pass a find_candidates `id` (GitHub login, ORCID iD, or source:name).
`handle`	Yes	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.

Output Schema

TableJSON 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.

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

A5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it reveals the return envelope (structuredContent with view=profile), instructs agents to consume only structuredContent, and explains the semantics of recent_activities: it's window-limited (2025–2026, ~20 events per project) and not a full career history. This prevents misinterpretation.

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 front-loads the core fetch purpose, then packs routing guidance and output-handling instructions into compact paragraphs. The 'IMPORTANT' caveat is the only prose beyond the functional contract and earns its place by preventing a common misinterpretation.

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?

For a lookup tool with an output schema, the description covers identifier resolution, alternative tool routing, return consumption, and data-window caveats. There is no obvious missing information an agent needs to select or call this tool correctly.

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?

Schema coverage is already 100%, and the description still adds value by clarifying the id alias behavior, exact accepted handle forms, and the rule not to fabricate GitHub handles for research/deep-tech people. This gives agents enough context to populate either parameter correctly.

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 opens with a specific verb and resource ('Fetch one contributor's profile card') and enumerates all accepted identifier forms. It also distinguishes itself from find_candidates, so an agent knows exactly what this tool is for.

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?

It explicitly says when not to use it — find_candidates already returns inline profiles — and when to use it: 'for ids outside those results or when the user asks for deeper detail.' It also instructs agents not to invent GitHub handles and to pass ids for research/deep-tech people.

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?