Skip to main content
Glama

Get My Profile

get_my_profile
Read-only

Returns the signed-in user's doola profile: their name, email, country of residence and phone number. A null field is not on file, which is a complete answer, not a failure. To change any of them, point the user to their doola dashboard. Answer in plain language and never show the user the field names.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a safe, non-destructive, closed-world read, so the safety profile is covered. The description adds genuinely useful behavior that annotations can't express: a null field means 'not on file' and is a complete answer rather than a failure, which prevents the agent from retrying or reporting an error. It also sets presentation rules (plain language, never expose internal field names).

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 tight sentences, front-loaded with what is returned, then the null-handling caveat, then the change-request redirect and presentation rule. Every sentence carries distinct information and none restates the title or annotations.

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?

For a simple, parameter-free read with no output schema, the description covers the returned fields, the ambiguous null case, and what to do when the user wants to modify data. An agent has everything needed to call it and interpret the response correctly.

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?

All three parameters are optional analytics fields (context, llm_model, conversation_id) and the schema documents each at 100% coverage, so the baseline is 3. The description adds nothing about them, but they are meta/telemetry inputs, not arguments that shape the query, so no meaningful semantics are missing.

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?

States a specific verb (returns) plus the exact resource and fields: the signed-in user's doola profile with name, email, country of residence and phone number. That 'signed-in user's profile' framing distinguishes it from the sibling tools that all deal with company, plan, invoice or compliance data rather than the person's own details.

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?

Gives clear routing for the out-of-scope case: to change any field, point the user to their doola dashboard rather than attempting a write here. What's slightly thin is an explicit 'call this when the user asks about their own name/email/phone' trigger, but the retrieval scope is unambiguous.

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.