Skip to main content
Glama

My profile (full)

profile_get
Read-onlyIdempotent

Your own client-portal profile exactly as the My profile page shows it: name, email with its verified date and any pending email change (masked), phone, About me, company, photo link, account type and roles, member since, and how complete the profile is. Only the signed-in account. Free text you typed is wrapped as data.

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": "profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the name shown. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: pending email change is masked, the response mirrors the portal page layout, and user-typed free text is wrapped as data (a prompt-injection safeguard). It does not discuss caching or account-state prerequisites, but the extra value is real.

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 core ident (own profile, full page-equivalent) followed by the field enumeration, then two short scoping sentences. The field list is long but each item earns its place by telling the agent what it can answer without a follow-up call; only minor tightening is possible.

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, and the description compensates by enumerating the returned fields and noting masking of pending email. Scope (signed-in account only), data-safety behavior and the locale parameter's effect via schema are all covered; only prerequisites such as authentication state go unstated.

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?

Only one optional parameter (locale) with 100% schema description coverage and an enum, so the schema fully documents it and the description adds nothing on this axis. The field named "Language of the name shown" is arguably self-explanatory, so baseline 3 applies; the description never references the locale option at all.

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?

States a specific resource and scope: "Your own client-portal profile exactly as the My profile page shows it," then enumerates the returned fields (name, email with verified date, phone, company, photo, roles, completeness). "Only the signed-in account" scopes it against team/profile-collection siblings, though it never names the closest alternative such as my_profile or team_profile_get_self.

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?

Usage is implied by the scope constraint "Only the signed-in account" and by the "full" framing in the title, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for fetching another person's profile or a lighter summary view. An agent must infer routing from sibling names alone.

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