Skip to main content
Glama
jun229

truemarkets-mcp-server

by jun229
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get account profile

tm_get_profile
Read-onlyIdempotent

Retrieve authenticated user profile details including email and associated wallet addresses for account management and verification.

Instructions

Get the authenticated user's profile including email and wallet addresses.

Returns: { email, wallets: [{ chain, address }] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/read.ts:189-202 (handler)
    The async function that handles the 'tm_get_profile' tool request, calling api.getProfile() and formatting the output.
    async () => {
  const profile = await api.getProfile();

  const wallets = (profile.wallets ?? []).map((w) => ({
    chain: w.chain === "evm" ? "base" : (w.chain ?? ""),
    address: w.address ?? "",
  }));

  const output = { email: profile.email ?? "", wallets };

  return {
    content: [{ type: "text", text: JSON.stringify(output, null, 2) }],
    structuredContent: output,
  };
  • src/tools/read.ts:174-188 (registration)
    Registration of the 'tm_get_profile' tool within the MCP server, including the schema and tool metadata.
      server.registerTool(
    "tm_get_profile",
    {
      title: "Get account profile",
      description: `Get the authenticated user's profile including email and wallet addresses.

Returns: { email, wallets: [{ chain, address }] }`,
      inputSchema: {},
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
    },

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Annotations already cover key behavioral traits (read-only, open-world, idempotent, non-destructive). The description adds value by specifying the return format ('{ email, wallets: [{ chain, address }] }'), which is useful context not provided in annotations. No contradiction with annotations.

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?

The description is front-loaded with the core purpose in the first sentence, followed by a concise return format specification. Both sentences earn their place by providing essential information without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), rich annotations, and clear return format in the description, it is nearly complete. A minor gap is lack of explicit usage guidance versus siblings, but overall it provides sufficient context for an agent to use 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 specific action ('Get') and resource ('the authenticated user's profile'), including what data is retrieved ('email and wallet addresses'). It distinguishes from siblings like tm_get_balances (which focuses on balances) and tm_get_price/quote (which are market-related).

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

Usage Guidelines3/5

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

The description implies usage for retrieving profile data, but does not explicitly state when to use this tool versus alternatives (e.g., no guidance on when profile info is needed vs. balances or assets). It provides basic context but lacks explicit when/when-not instructions or named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jun229/tm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server