Skip to main content
Glama

My profile

my_profile
Read-onlyIdempotent

The full profile of the signed-in Barmaan user (your own data): name, email, phone, company, account type, staff roles, preferences, mailboxes, customer groups, member since, and this connection's scopes. No passwords or tokens.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — which it does by enumerating the returned fields and explicitly stating 'No passwords or tokens.' That privacy note is genuinely useful added information; it stops short of describing failure modes (e.g. unauthenticated calls) but the safety surface is well covered.

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?

A single dense sentence with the resource front-loaded and the field list serving double duty as an output preview; the closing exclusion ('No passwords or tokens') is short and earns its place. No filler, no restatement of the title.

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?

With no output schema and no parameters, the description carries the burden of telling the agent what comes back, which it does via the field enumeration. The only shortfall is that it does not clarify format, volume, or how to distinguish this from the other self/profile tools in the catalog.

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 is 4 and there is nothing for the description to disambiguate. The field inventory usefully implies what the empty-input call yields, though it is a return-value preview rather than parameter meaning.

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: 'the full profile of the signed-in Barmaan user (your own data)', followed by an explicit inventory of what is returned. The self-scoped framing implicitly separates it from generic profile lookups, but it never names or contrasts with siblings like profile_get or team_profile_get_self, leaving that differentiation to inference.

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?

The parenthetical '(your own data)' and the scopes mention hint at when this is appropriate (identifying the current caller / connection), but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer that profile_get or team_profile_get_self covers other cases.

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