Bernuvia

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The account's name.
`email`	Yes	The account's email.
`handle`	Yes	Public @handle of the account.
`isSeller`	Yes	Whether the seller scope may be used TODAY with this token.
`prefLang`	Yes	Preferred language, or null.
`avatarUrl`	Yes	Avatar URL, or null.
`prefTheme`	Yes	Preferred theme (light or dark), or null.
`accountType`	Yes	What kind of credential is calling.
`ownerWallet`	Yes	The wallet of the ACCOUNT you act on (for a delegate, its owner's), or null.
`payerWallet`	Yes	The wallet that really pays and signs, or null if it does not exist yet.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

removedOutput schema / properties / wallet

Removed value: -{
-  "description": "DEPRECATED alias of `ownerWallet`, with the same value.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "email",
-  "name",
-  "handle",
-  "wallet",
-  "avatarUrl",
-  "prefLang",
-  "prefTheme",
-  "ownerWallet",
-  "accountType",
-  "isSeller",
-  "payerWallet"
-]New value: +[
+  "email",
+  "name",
+  "handle",
+  "avatarUrl",
+  "prefLang",
+  "prefTheme",
+  "ownerWallet",
+  "accountType",
+  "isSeller",
+  "payerWallet"
+]

Changed11 schema fields changedSep 23, 2026

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."

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does substantial work: it enumerates the returned fields (email, name, handle, language, ownerWallet, payerWallet, accountType, isSeller) and, crucially, discloses the semantic constraint that ownerWallet is present but 'YOU cannot use to pay' while yours arrives in payerWallet and agentWallet is absent. It does not state read-only/auth/rate-limit behavior, but for a no-arg read tool that is minor.

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-loads the core statement of purpose before the exclusions, and every clause carries routing or field information. Slightly weakened by the dense wallet clauses ('Yours comes right here in payerWallet, as in my_capabilities and my_balance'), which are harder to parse than the rest.

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?

An output schema exists, so raw return values need not be re-explained; the description instead supplies the semantic meaning of ambiguous fields (accountType for a delegate, the wallet distinctions). Combined with the explicit sibling routing, an agent has everything needed to call and interpret this tool.

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 of 4 applies. There are no argument semantics to add meaning to, and the description correctly spends its words on return content and sibling differentiation instead.

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 names a specific resource ('YOUR OWNER's PROFILE DATA') and explicitly frames what the tool is for ('the tool to pick when what you need is the data that account presents itself with'). It distinguishes itself from close siblings by naming my_capabilities and my_balance and explaining the boundary, so an agent can select it without opening any schema.

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?

Explicit when-to-use ('the tool to pick when...') plus multiple when-NOT clauses routing to named alternatives: scopes/sell-today go to my_capabilities, balances go to my_balance. This is textbook three-way routing with no inference required.

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

All Bernuvia tools Inspect

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

Need Help?