Skip to main content
Glama

My Account Details

tt_get_my_profile
Read-onlyIdempotent

The signed-in user's own Tradetron account details: name, email, and registered phone number (plus user_id and member-since date).

The phone arrives in THREE fields: mobile (the number), country_code, and phone, which is the two joined. To answer "which number do my alerts go to?", quote phone — it is the whole number; mobile alone is missing the country code.

Use for "what's my registered email?", "which number do my alerts go to?", "what name is on my account?", or when confirming the account you're acting on before a write. Read-only.

This only ever returns the CALLER's own details — there is no way to look up another user, so don't offer it.

AUTH-REQUIRED: returns the connect funnel when no Tradetron account is connected. Never guess or recall these values from conversation — read them here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond them: the AUTH-REQUIRED connect-funnel behavior when no account is linked, and an explicit anti-hallucination instruction to read values here rather than recall them from conversation. The three-field phone decomposition is genuinely useful behavior disclosure, though it is framed as answer formatting rather than tool mechanics.

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-loaded with the payload summary before the field caveat and the usage triggers, so an agent gets the essentials immediately. The phone-explanation paragraph is slightly over-explained (repeats that `phone` is the whole number twice) and the line breaks read as prose pasted into a 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?

There is no output schema, so the description must carry return-value semantics and it does: it names the returned fields and explains the phone field composition well enough to answer correctly. The auth failure path and the single-user scope complete the picture for a zero-parameter read 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?

Zero parameters, so there is nothing for the description to disambiguate — baseline 4 applies. The discussion of `mobile`, `country_code`, and `phone` concerns returned fields rather than inputs, which is helpful but belongs more to output semantics than parameter semantics.

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 and resource (returns the signed-in user's own Tradetron account details) and enumerates the exact fields returned: name, email, phone, user_id, member-since. It also draws a hard boundary against sibling lookups — 'there is no way to look up another user' — so an agent can distinguish it from tools like tt_get_my_brokers without opening the 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?

Gives concrete trigger utterances ("what's my registered email?", "which number do my alerts go to?", "what name is on my account?") plus a workflow cue: use it when confirming the acting account before a write. It also states when not to use it ('don't offer it' for other users), which is the exclusion guidance most definitions lack.

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