Skip to main content
Glama

Alina Szaputko — Online Consultation Booking

Get Alina Szaputko professional profile

get_professional_profile
Read-onlyIdempotent

Read-only. Retrieve Alina Szaputko’s public professional profile, qualifications, services, languages, consultation price, booking rules and policy links. This tool cannot create or change appointments or payments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real value by stating the negative capability boundary ('cannot create or change appointments or payments'), which prevents an agent from assuming side effects. It does not mention rate limits, auth requirements, or whether profile data can change between calls, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the 'Read-only.' safety signal, then the retrieved content, then the negative boundary. Every sentence carries distinct information and none restates the tool name or annotations verbatim.

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?

There is no output schema, so the description bears the burden of describing return values — and it does so by listing the categories of data returned (qualifications, services, languages, price, booking rules, policy links). It does not describe the shape or format of the response, which is the remaining gap for a tool with no output schema, but an agent has enough to decide to call it and to interpret what comes back.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate at the argument level. It correctly implies the tool is scoped to a single fixed professional rather than accepting an identifier, which is the only semantic point a zero-param schema leaves open.

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 gives a specific verb ('Retrieve') and a precise resource ('Alina Szaputko's public professional profile'), then enumerates the contents — qualifications, services, languages, consultation price, booking rules, policy links. That enumeration distinguishes it from sibling read tools like get_agent_booking_status, whose name implies appointment/status data rather than profile attributes.

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

Usage Guidelines4/5

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

Usage context is clear: this is the read path for profile/price/policy information, and the closing sentence explicitly rules out creating or changing appointments or payments, which steers an agent away from create_checkout_session. It stops short of naming an alternative or stating a positive trigger condition ('use this before booking to confirm price and policy'), so it is clear context without full routing guidance.

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