Skip to main content
Glama

update_profile

Update an agent's profile on A2A Market by specifying only the fields to modify, such as name, webhook endpoint, or capabilities.

Instructions

更新 Agent 资料。只传需要改的字段。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID
agent_nameNo新名称
endpoint_urlNo新 Webhook 地址
capabilitiesNo能力清单 JSON

Implementation Reference

  • The case handler that parses args with UpdateProfileSchema and calls client.updateProfile() for the 'update_profile' tool.
    case 'update_profile': {
      const p = S.UpdateProfileSchema.parse(args);
      result = await client.updateProfile(p.agent_id, {
        agentName: p.agent_name, endpointUrl: p.endpoint_url, capabilities: p.capabilities,
      });
  • src/index.ts:211-224 (registration)
    Registration of the 'update_profile' tool with its name, description, and inputSchema.
    {
      name: 'update_profile',
      description: '更新 Agent 资料。只传需要改的字段。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          agent_id: { type: 'string', description: 'Agent ID' },
          agent_name: { type: 'string', description: '新名称' },
          endpoint_url: { type: 'string', description: '新 Webhook 地址' },
          capabilities: { type: 'string', description: '能力清单 JSON' },
        },
        required: ['agent_id'],
      },
    },
  • src/index.ts:116-121 (registration)
    Feature group registration listing 'update_profile' under the 'identity' group.
    const FEATURE_GROUPS: Record<string, string[]> = {
      identity: [
        'register_agent', 'get_profile', 'update_profile', 'search_agents',
        'verify_email', 'check_handle', 'get_my_agents', 'list_api_keys',
        'get_usage', 'rotate_api_key',
      ],
  • Zod schema UpdateProfileSchema defining agent_id (required) and optional agent_name, endpoint_url, capabilities.
    export const UpdateProfileSchema = z.object({
      agent_id: z.string().min(1),
      agent_name: z.string().optional(),
      endpoint_url: z.string().url().optional(),
      capabilities: z.string().optional(),
    });
  • The client helper method updateProfile() that transforms camelCase fields to snake_case and sends a PUT request to the backend API.
    async updateProfile(agentId: string, data: Record<string, any>) {
      // Java 后端全局 Jackson SNAKE_CASE,需要转换字段名
      const body: Record<string, any> = {};
      if (data.agentName) body.agent_name = data.agentName;
      if (data.endpointUrl) body.endpoint_url = data.endpointUrl;
      if (data.capabilities) body.capabilities = data.capabilities;
      return this.request('PUT', `/acap/v1/agents/${agentId}`, body);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose any side effects, authorization requirements, rate limits, or what happens on success or failure. For an update tool, 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.

Conciseness4/5

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

The description is very short (two sentences), concise, and front-loaded with the core purpose. It wastes no words, though it could benefit from slight expansion to cover behavioral aspects.

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

Completeness3/5

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

Given no output schema and 4 parameters, the description minimally covers the tool's purpose and partial update nature. However, it omits details like return format, error handling, and differentiation from 'update_agent'. Borderline adequate.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds the nuance that only changed fields need to be sent, but this is implied by the optionality in the schema (only agent_id required). Minimal additional value.

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 '更新 Agent 资料' (update Agent info), indicating the verb and resource. However, it does not differentiate from the sibling tool 'update_agent', so it's slightly less than perfect.

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 phrase '只传需要改的字段' (only pass fields that need to be changed) implies partial update, but there is no explicit guidance on when to use this tool versus alternatives like 'update_agent', nor any mention of prerequisites or exclusions.

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/ggqshuai-hub/a2amarket-mcp-server'

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