Skip to main content
Glama

set_comp

DestructiveIdempotent

Record recruiter-stated pay details and career notes for a job so comparisons and tracking stay accurate; only supplied fields change, and empty strings clear existing values.

Instructions

Keep what a recruiter told the person about pay for a job, so get_comps can put it next to the others, and what the job is for their career (role, career_note). Only the fields given change; an empty string clears one. Write amounts the way they were said ("165-195K", "$215,000"): the first amount found is read to mark the highest. Returns what is kept for the job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "set_comp"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe job: its key as other tools return it (source:board:posting id, e.g. greenhouse:acme:4012345), just the posting id, or the company's name when that names one job (the one queued or applied to there). When it matches several, the error lists their keys.
baseNoThe base salary (range) the recruiter gave, as said: "165-195K". An empty string clears it.
noteNoA few words ("195K most likely their max"). Replaces the old note. Empty clears it.
roleNoWhat the job is, for its career value: product (builds the company's own product), customer (forward-deployed, solutions, customer-facing engineering) or internal (builds internal tools or platforms for the business). Empty clears it.
askedNoWhat the person asked for ("210-230K"). Empty clears it.
bonusNoBonus, as said ("10% target"). Empty clears it.
equityNoEquity, as said ("40K RSUs over 4 years"). Empty clears it.
signonNoSign-on bonus, as said. Empty clears it.
offeredNoWhat they offered. Empty clears it.
glassdoorNoThe pay Glassdoor shows for this job, as the person read it there ("170-210K"). Only a figure they typed in: jobwatch never fetches Glassdoor. Empty clears it.
career_noteNoA few words on its career value ("observability product, staff IC"). Empty clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / glassdoor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The pay Glassdoor shows for this job, as the person read it there (\"170-210K\"). Only a figure they typed in: jobwatch never fetches Glassdoor. Empty clears it.",
      +  "title": "Glassdoor"
      +}
  2. Addedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: partial update ('only the fields given change'), clearing via empty string, and format-dependent parsing ('the first amount found is read to mark the highest'). It also says it returns what is kept, though it does not spell out what an empty-string clear does to the highest-marked value.

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?

Tight, front-loaded, and every clause carries information. The first sentence is convoluted with its 'and what the job is for their career' tack-on, which slightly hurts readability.

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?

For an 11-parameter mutation with no output schema, the description covers partial semantics, clearing, format expectations, return behavior, and the ambiguous-key failure mode. Missing only edge behavior such as how conflicting values (offered vs. base) are ranked.

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 coverage is 100% and each field already documents the empty-string clear convention. The description only adds the amount-format convention ('165-195K'), which is genuinely useful but marginal against an already rich schema.

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 concrete verb and resource ('Keep what a recruiter told the person about pay for a job') plus the career fields, and names the sibling it feeds (get_comps). An agent can distinguish it from get_comps without inspecting either schema.

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

Usage Guidelines4/5

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

Makes clear this is the write side that get_comps reads back, and the key description explains the ambiguous-match error. It never states when not to use it or what to do instead, so it stops short of full routing guidance.

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