Skip to main content
Glama

Perfil do usuário

get_profile
Read-only

Retorna o perfil completo do usuário autenticado: dados cadastrais, negócio (CNPJ/website, se hasBusiness), plano e status de assinatura (Stripe), e vínculo com planejador (plannerId). Único campo omitido é phone, redigido antes de sair do servidor MCP — mesmo que fosse pedido explicitamente, não é devolvido.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
idNo
cepNo
nameNo
planNo
slugNo
typeNo
emailNo
auth0IdNo
pictureNo
currencyNo
locationNo
createdAtNo
plannerIdNo
updatedAtNo
coverImageNo
occupationNo
hasBusinessNo
businessCnpjNo
businessNameNo
menuPreferenceNo
businessWebsiteNo
stripeCustomerIdNo
subscriptionStatusNo
onboardingCompletedNo
stripeSubscriptionIdNo
subscriptionCurrentPeriodEndNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already signal read-only and non-destructive behavior, and the description adds a valuable behavioral detail: the phone field is redacted server-side and will never be returned even if requested. This goes beyond the structured metadata and prevents the agent from expecting data that will never exist.

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 delivers the resource, the full field list, and the key redaction caveat with no filler. Information is front-loaded and the caveat is logically appended without bloating the description.

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 no-parameter read-only tool with an output schema available, the description is complete: it identifies the target user, lists the returned data, and states the one notable omission. Nothing else is needed for an agent to call it correctly.

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 has zero parameters and the input schema coverage is 100%, so there is no parameter documentation burden on the description. The description appropriately focuses on the return payload instead of inventing parameter guidance.

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 states a specific verb ('Retorna') and a well-defined resource: the complete profile of the authenticated user, enumerating the exact data groups returned (registro, negócio, plano/assinatura, plannerId). This makes it unmistakably distinct from the sibling update_profile and other read-only tools.

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?

The description makes clear this is the tool for fetching the authenticated user's full profile, and the read-only naming reinforces when it applies. It does not explicitly name alternatives or exclusion cases, but for a zero-parameter getter the intended context is clear.

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.