Skip to main content
Glama

update_salary

Update salary and compensation details including base pay, bonuses, stocks, and target salary for job application tracking.

Instructions

Update your salary/compensation details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNoCurrency code. Use get_currencies to look up valid codes (e.g., 2 = INR, 3 = USD)
baseNoBase salary
stocksNoAnnual stock/equity value
bonusNoAnnual bonus
signingBonusNoSigning bonus
targetSalaryNoTarget salary

Implementation Reference

  • The handler function for updating salary, which takes currency, base, stocks, bonus, signingBonus, and targetSalary as arguments and calls client.updateProfileSalary.
    async (args) => {
      const salaryData: Record<string, unknown> = {};
      if (args.currency !== undefined) { salaryData.currency = args.currency; }
      if (args.base !== undefined) { salaryData.base = args.base; }
      if (args.stocks !== undefined) { salaryData.stocks = args.stocks; }
      if (args.bonus !== undefined) { salaryData.bonus = args.bonus; }
      if (args.signingBonus !== undefined) { salaryData.signingBonus = args.signingBonus; }
      if (args.targetSalary !== undefined) { salaryData.targetSalary = args.targetSalary; }
      await client.updateProfileSalary(salaryData);
      return { content: [{ type: 'text' as const, text: JSON.stringify({ message: 'Salary updated successfully', updatedFields: Object.keys(salaryData) }, null, 2) }] };
    }
  • Input schema for update_salary using Zod.
    {
      currency: z.number().optional().describe('Currency code. Use get_currencies to look up valid codes (e.g., 2 = INR, 3 = USD)'),
      base: z.number().optional().describe('Base salary'),
      stocks: z.number().optional().describe('Annual stock/equity value'),
      bonus: z.number().optional().describe('Annual bonus'),
      signingBonus: z.number().optional().describe('Signing bonus'),
      targetSalary: z.number().optional().describe('Target salary'),
    },
  • Tool registration for update_salary within registerProfileTools.
    server.tool(
      'update_salary',
      'Update your salary/compensation details',
      {
        currency: z.number().optional().describe('Currency code. Use get_currencies to look up valid codes (e.g., 2 = INR, 3 = USD)'),
        base: z.number().optional().describe('Base salary'),
        stocks: z.number().optional().describe('Annual stock/equity value'),
        bonus: z.number().optional().describe('Annual bonus'),
        signingBonus: z.number().optional().describe('Signing bonus'),
        targetSalary: z.number().optional().describe('Target salary'),
      },
      async (args) => {
        const salaryData: Record<string, unknown> = {};
        if (args.currency !== undefined) { salaryData.currency = args.currency; }
        if (args.base !== undefined) { salaryData.base = args.base; }
        if (args.stocks !== undefined) { salaryData.stocks = args.stocks; }
        if (args.bonus !== undefined) { salaryData.bonus = args.bonus; }
        if (args.signingBonus !== undefined) { salaryData.signingBonus = args.signingBonus; }
        if (args.targetSalary !== undefined) { salaryData.targetSalary = args.targetSalary; }
        await client.updateProfileSalary(salaryData);
        return { content: [{ type: 'text' as const, text: JSON.stringify({ message: 'Salary updated successfully', updatedFields: Object.keys(salaryData) }, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' implying a mutation, but doesn't mention permissions needed, whether changes are reversible, or what happens to existing salary data not included in the update. This is inadequate for a mutation tool with zero annotation coverage.

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 with no wasted words, making it easy to parse and front-loaded with the core action. Every word earns its place, achieving optimal conciseness.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the update affects (e.g., user profile, job application), success conditions, or return values, leaving significant gaps 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.

Parameters3/5

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

The input schema has 100% description coverage, providing clear details for all 6 parameters (e.g., 'currency' with code examples). The description adds no additional parameter semantics beyond the schema, so it meets the baseline of 3 without compensating or detracting.

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 the resource ('your salary/compensation details'), making the tool's purpose understandable. However, it doesn't differentiate from sibling tools like 'update_profile' or 'get_salary' that might handle related data, so it's not a perfect 5.

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 like 'update_profile' (which might include salary) or 'get_salary' (for reading). It lacks context on prerequisites, such as whether a user profile must exist first, leaving usage ambiguous.

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/6figr-com/job-gpt-mcp-server'

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