Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_profile

YOUR OWNER's PROFILE DATA (you act as them): the tool to pick when what you need is the data that account presents itself with. Do NOT use it for your scopes or to find out whether you may sell today: that is my_capabilities. Do NOT use it for balances: that is my_balance. It carries their email, name, handle and language, and in ownerWallet their in-app wallet, which YOU cannot use to pay. Yours comes right here in payerWallet, as in my_capabilities and my_balance; agentWallet, on the other hand, does NOT travel in the profile. It also carries accountType, which for you is "delegate", and isSeller. wallet is still sent with the same value as a DEPRECATED alias.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe account's name.
emailYesThe account's email.
handleYesPublic @handle of the account.
walletYesDEPRECATED alias of `ownerWallet`, with the same value.
isSellerYesWhether the seller scope may be used TODAY with this token.
prefLangYesPreferred language, or null.
avatarUrlYesAvatar URL, or null.
prefThemeYesPreferred theme (light or dark), or null.
accountTypeYesWhat kind of credential is calling.
ownerWalletYesThe wallet of the ACCOUNT you act on (for a delegate, its owner's), or null.
payerWalletYesThe wallet that really pays and signs, or null if it does not exist yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedOutput schema / properties / accountType / description
      Previous value: -"Qué clase de credencial llama."New value: +"What kind of credential is calling."
    • changedOutput schema / properties / avatarUrl / description
      Previous value: -"URL del avatar, o null."New value: +"Avatar URL, or null."
    • changedOutput schema / properties / email / description
      Previous value: -"Correo de la cuenta."New value: +"The account's email."
    • changedOutput schema / properties / handle / description
      Previous value: -"@handle público de la cuenta."New value: +"Public @handle of the account."
    • changedOutput schema / properties / isSeller / description
      Previous value: -"Si HOY se puede usar el ámbito seller con este token."New value: +"Whether the seller scope may be used TODAY with this token."
    • changedOutput schema / properties / name / description
      Previous value: -"Nombre de la cuenta."New value: +"The account's name."
    • changedOutput schema / properties / ownerWallet / description
      Previous value: -"La wallet de la CUENTA sobre la que se actúa (para un delegado, la de su dueño), o null."New value: +"The wallet of the ACCOUNT you act on (for a delegate, its owner's), or null."
    • changedOutput schema / properties / payerWallet / description
      Previous value: -"La wallet con la que se paga y se firma de verdad, o null si aún no existe."New value: +"The wallet that really pays and signs, or null if it does not exist yet."
    • changedOutput schema / properties / prefLang / description
      Previous value: -"Idioma preferido, o null."New value: +"Preferred language, or null."
    • changedOutput schema / properties / prefTheme / description
      Previous value: -"Tema preferido (light o dark), o null."New value: +"Preferred theme (light or dark), or null."
    • changedOutput schema / properties / wallet / description
      Previous value: -"ALIAS RETIRADO de `ownerWallet`, con su mismo valor."New value: +"DEPRECATED alias of `ownerWallet`, with the same value."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral details: ownerWallet cannot be used to pay, payerWallet is the agent's wallet, agentWallet does not travel in the profile, accountType is 'delegate', and wallet is a deprecated alias. This goes well beyond a simple 'returns profile data' statement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is information-dense but somewhat sprawling and repetitive. It front-loads the core purpose well, but the wallet explanation meanders ('Yours comes right here in payerWallet, as in my_capabilities and my_balance; agentWallet, on the other hand, does NOT travel in the profile'). Every sentence adds value, but the structure could be tightened.

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 zero-parameter read-only profile tool with an output schema, the description covers the essential decision factors: what data it returns, which sibling tools to use instead, and the critical caveat that ownerWallet cannot be used to pay. Nothing an agent needs to select or invoke this tool correctly is missing.

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 schema coverage is 100%, so there is nothing to document. The description instead explains the meaning of the returned fields, which is valuable context for an agent deciding whether this tool answers its need. Baseline 4 for zero-param tools is appropriate.

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 clearly states the tool returns the owner's profile data and explicitly distinguishes it from my_capabilities and my_balance. It names the specific fields carried (email, name, handle, language, ownerWallet, payerWallet, accountType, isSeller), making the purpose unmistakable.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance ('the tool to pick when what you need is the data that account presents itself with') and explicit when-not-to-use guidance with named alternatives ('Do NOT use it for your scopes... that is my_capabilities. Do NOT use it for balances: that is my_balance.'). This is exemplary routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bernuvia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources