Skip to main content
Glama

Alisa Chebotarenko — AI & IT Advisory

get_profile

Get Alisa Chebotarenko profile, certifications (PMP, PSPO I, AWS AI Practitioner), Europe & Asia availability, spoken languages (EN/RU/IT), equivalent roles, the 4 core domains, and direct contact details.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoPreferred response language (en or ru).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals that the response includes direct contact details (a mild sensitivity note) but never states that the call is read-only, side-effect free, or what the response shape looks like. For a low-risk getter this is adequate but thin.

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?

A single dense sentence with zero filler, front-loaded on the resource and then the payload contents. The comma-list of items is slightly scannable-unfriendly but every item earns its place by telling the agent what it will receive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

One optional parameter, no output schema, so the description's job is mainly to preview return contents, which it does in detail. The only shortfall is not clarifying the lang parameter's effect or stating that the call is read-only, minor for a tool of this complexity.

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?

The single lang parameter is fully described in the schema (enum en/ru, "Preferred response language"), so the baseline is 3. The description does nothing to reinforce it and in fact risks confusion by listing spoken languages (EN/RU) in the same parenthetical style, without clarifying that lang selects response language rather than filtering by language.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource ("Get ... profile") with an explicit enumeration of what the profile contains: certifications, availability, languages, equivalent roles, core domains, contact details. An agent can tell this is the person/candidate profile reader rather than a generic lookup or any of the sibling listers. It stops short of naming a sibling to distinguish itself from, so 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not statement, and no routing to list_services or submit_inquiry. Usage is only implied by the enumerated contents, which tell an agent it is the right call when it needs credentials, availability, or contact info.

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