Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

generate_salary_negotiation_script

Generate salary negotiation talking points and email templates from your current offer, target salary, and justification points.

Instructions

Generate salary negotiation talking points and email templates.

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": {
      "current_offer": "<current_offer>",
      "target_salary": "<target_salary>"
    },
    "name": "generate_salary_negotiation_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
current_offerYesCurrent offer amount
target_salaryYesTarget salary amount
justificationNoJustification points for the negotiation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description must cover behavioral traits. It only states 'generate' without any mention of side effects, auth requirements, or output format. This is insufficient for a tool that creates content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single 7-word sentence, which is concise but lacks structure or front-loading of key information. It could benefit from additional context without being verbose.

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 no output schema, the description should explain what the generated output looks like (e.g., format, structure). It does not, and also lacks any behavioral context, making it incomplete for an agent to understand the tool fully.

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 covers all parameters with descriptions, achieving 100% coverage. The description adds no extra meaning beyond the schema; it doesn't explain how parameters influence output. Baseline score of 3 is appropriate.

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 that the tool generates salary negotiation talking points and email templates. The verb 'generate' and the resource 'salary negotiation script' are specific, but it does not differentiate from sibling tools like 'analyze_offer' or 'get_market_comp' by describing unique use cases.

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?

No guidance is provided on when or when not to use this tool. Alternatives or prerequisites are not mentioned, leaving the agent to infer usage context.

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

Deploy Server

Other Tools