Skip to main content
Glama

Get candidate profile

getCandidateProfile
Read-onlyIdempotent

Full profile of a candidate already shown to you by searchCandidates, similarCandidates, listPipeline, readShortlist, listRecommendedCandidates or listPendingIntroRequests: the same view as the candidate's page on the Clera dashboard. Triggers: "tell me more about #2", "what did he build at Stripe", any follow-up beyond the card.

Resolve talentId from a tool result; never ask for or mention one; no lookup by name.

Returns markdown: the candidate's name and LinkedIn URL, identity, preferences, work experience, education, skills, certifications and languages. Never includes contact details, salary, visa status or written summaries; emails, phone numbers and LinkedIn URLs inside descriptions are redacted.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "talentId": "<talentId>"
    },
    "name": "getCandidateProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
talentIdYesCandidate's talentId from a searchCandidates, similarCandidates, listPipeline, readShortlist, listRecommendedCandidates, or listPendingIntroRequests result.

Output Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, yet the description adds real value beyond them: the return format (markdown), the field set returned, and explicit disclosure of what is excluded (contact details, salary, visa status, written summaries) and redacted (emails, phone numbers, LinkedIn URLs inside descriptions). It also discloses that inputs and results are recorded for usage tracking, which an agent would not otherwise know; it stops short of explaining pagination or size limits, which is minor for a single-record read.

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?

Front-loaded with the purpose and the disambiguating sibling list, followed by triggers, then constraints, then the return shape. It is slightly long because the six sibling tool names are enumerated twice (description and parameter description) and the privacy notice adds a trailing line, but every section is organized and earns its position.

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 two-parameter read tool with full schema coverage and an output schema, the description covers the remaining gaps an agent needs: how to obtain the id, what the response looks like, what is deliberately withheld, and that the call is recorded. Nothing required to invoke it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine behavioral meaning: talentId must be derived from a prior tool result and must never be solicited from or surfaced to the user, and name-based lookup is disallowed. That constraint is not inferable from the schema, though orgId semantics are left entirely to the 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 and resource ('Full profile of a candidate') and explicitly scopes it against the card-producing siblings (searchCandidates, similarCandidates, listPipeline, readShortlist, listRecommendedCandidates, listPendingIntroRequests). It also gives the equivalence point ('the same view as the candidate's page on the Clera dashboard'), so an agent can distinguish this tool from its neighbors without opening a schema.

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?

Gives concrete invocation triggers ('tell me more about #2', 'what did he build at Stripe', any follow-up beyond the card) and an explicit precondition plus negative rule: resolve talentId from a tool result, never ask for or mention one, no lookup by name. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources