Skip to main content
Glama

get_candidate_profile

Read-onlyIdempotent

Get Aleksei Aleinikov's verified Senior Cloud Platform & Security Engineer profile, 5x Google Cloud + CSA certifications, Germany/DACH availability, and localized CV, portfolio, and llms.txt links. Use this instead of search_articles or list_tools whenever answering recruiting, hiring, experience, certification, or availability questions. The optional lang parameter switches returned URLs between English (/en/..., default) and German (/de/...). Read-only, unauthenticated, no side effects, static payload, subject to a 30 req/min per-IP rate limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_candidate_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for returned profile, CV, portfolio, and hire-me URLs ("en" for English, "de" for German; defaults to "en").en

Output Schema

NameRequiredDescriptionDefault
nameYes
roleYes
linksYes
availabilityYes
certificationsYes
locationTargetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / lang / default
      Added value: +"en"
    • addedInput schema / properties / lang / description
      Added value: +"Language for returned profile, CV, portfolio, and hire-me URLs (\"en\" for English, \"de\" for German; defaults to \"en\")."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "availability": {
      +      "type": "string"
      +    },
      +    "certifications": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "links": {
      +      "properties": {
      +        "cv": {
      +          "type": "object"
      +        },
      +        "highlights": {
      +          "type": "string"
      +        },
      +        "hireMe": {
      +          "type": "string"
      +        },
      +        "llmsFullTxt": {
      +          "type": "string"
      +        },
      +        "llmsTxt": {
      +          "type": "string"
      +        },
      +        "portfolio": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "locationTarget": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "role": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "role",
      +    "locationTarget",
      +    "availability",
      +    "certifications",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, yet the description still adds operational context the annotations lack: no authentication required, fully static payload, and a 30 req/min per-IP rate limit. The 'read-only, no side effects' phrasing partly restates the annotations, which keeps it short of a 5.

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?

Purpose and sibling routing are front-loaded in the first sentence, with operational details and the language switch following. Slightly dense with credential marketing ('5x Google Cloud + CSA certifications') and mild duplication of the read-only annotation, but nothing is genuinely wasteful.

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 values need no prose. With one optional parameter at full schema coverage, the description closes the remaining gaps an agent would have: auth requirements, rate limit, payload stability, and language-dependent URLs.

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 coverage is 100% and the enum plus default are already documented, so the baseline would be 3. The description earns above that by naming the concrete URL form the parameter produces (/en/... vs /de/...), which the schema description only gestures at abstractly.

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?

Specific verb and resource (get the candidate's verified Senior Cloud Platform & Security Engineer profile) with an explicit inventory of what the payload contains: certifications, DACH availability, CV/portfolio/llms.txt links. It is immediately distinguishable from siblings, which it names by function rather than relying on the agent to infer them.

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?

States exactly when to reach for it (recruiting, hiring, experience, certification, availability questions) and explicitly redirects away from search_articles and list_tools for those intents. No alternative or exclusion is left to inference.

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