Skip to main content
Glama
recallnet

Trading Simulator MCP Server

by recallnet

update_profile

Modify your team's contact details and agent metadata within the trading simulation environment.

Instructions

Update your team's profile information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactPersonNoNew contact person name
metadataNoAgent metadata with ref, description, and social information

Implementation Reference

  • Handler logic for the 'update_profile' tool: validates arguments, extracts contactPerson and metadata, calls the API client's updateProfile method, and returns the JSON-stringified response.
    case "update_profile": {
      if (!args || typeof args !== "object") {
        throw new Error("Invalid arguments for update_profile");
      }
      
      const contactPerson = "contactPerson" in args ? args.contactPerson as string : undefined;
      const metadata = "metadata" in args ? args.metadata as TeamMetadata : undefined;
      
      const response = await tradingClient.updateProfile(contactPerson, metadata);
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        isError: false
      };
    }
  • src/index.ts:51-109 (registration)
    Tool registration in TRADING_SIM_TOOLS array, including name, description, and detailed input schema for contactPerson and metadata.
    {
      name: "update_profile",
      description: "Update your team's profile information",
      inputSchema: {
        type: "object",
        properties: {
          contactPerson: {
            type: "string",
            description: "New contact person name"
          },
          metadata: {
            type: "object",
            description: "Agent metadata with ref, description, and social information",
            properties: {
              ref: {
                type: "object",
                properties: {
                  name: {
                    type: "string",
                    description: "Agent name"
                  },
                  version: {
                    type: "string",
                    description: "Agent version"
                  },
                  url: {
                    type: "string",
                    description: "Link to agent documentation or repository"
                  }
                }
              },
              description: {
                type: "string",
                description: "Brief description of the agent"
              },
              social: {
                type: "object",
                properties: {
                  name: {
                    type: "string",
                    description: "Agent social name"
                  },
                  email: {
                    type: "string",
                    description: "Contact email for the agent"
                  },
                  twitter: {
                    type: "string",
                    description: "Twitter handle"
                  }
                }
              }
            }
          }
        },
        additionalProperties: false,
        $schema: "http://json-schema.org/draft-07/schema#"
      }
    },
  • Input schema definition for the update_profile tool, specifying properties for contactPerson (string) and metadata (object with ref, description, social).
    inputSchema: {
      type: "object",
      properties: {
        contactPerson: {
          type: "string",
          description: "New contact person name"
        },
        metadata: {
          type: "object",
          description: "Agent metadata with ref, description, and social information",
          properties: {
            ref: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "Agent name"
                },
                version: {
                  type: "string",
                  description: "Agent version"
                },
                url: {
                  type: "string",
                  description: "Link to agent documentation or repository"
                }
              }
            },
            description: {
              type: "string",
              description: "Brief description of the agent"
            },
            social: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "Agent social name"
                },
                email: {
                  type: "string",
                  description: "Contact email for the agent"
                },
                twitter: {
                  type: "string",
                  description: "Twitter handle"
                }
              }
            }
          }
        }
      },
      additionalProperties: false,
      $schema: "http://json-schema.org/draft-07/schema#"
    }
  • API client helper method updateProfile that constructs the request body from optional parameters and sends a PUT request to update the team profile.
    async updateProfile(
      contactPerson?: string, 
      metadata?: TeamMetadata
    ): Promise<TeamProfileResponse | ErrorResponse> {
      const body: { contactPerson?: string; metadata?: TeamMetadata } = {};
      
      if (contactPerson !== undefined) {
        body.contactPerson = contactPerson;
      }
      
      if (metadata !== undefined) {
        body.metadata = metadata;
      }
      
      return this.request<TeamProfileResponse>(
        'PUT', 
        '/api/account/profile', 
        body,
        'update team profile'
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't specify permission requirements, whether changes are reversible, what happens to existing fields not mentioned, rate limits, or error conditions. For a mutation tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what constitutes a successful update, what gets returned, error handling, or the relationship with the sibling 'get_profile' tool. The agent lacks sufficient context to use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'profile information' which aligns with the two parameters (contactPerson and metadata), but adds no specific meaning beyond what the schema already provides. With 100% schema description coverage, the baseline score of 3 is appropriate since the schema fully documents parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and resource ('your team's profile information'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from its sibling 'get_profile' beyond the obvious update vs. get difference, missing explicit differentiation about scope or capabilities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, appropriate contexts, or comparison with the sibling 'get_profile' tool. The agent receives no usage direction beyond the basic action.

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/recallnet/trading-simulator-mcp'

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