Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Analyze a job offer

analyze_offer
Read-onlyIdempotent

Compare a job offer with the market and get negotiation advice. Accepts either an amount (+currency, +period) or pasted offer-letter text. Says where the offer sits (percentile), what components matter, India in-hand estimate for INR, and what to negotiate. Needs a role.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoRole of the offer.
amountNoOffer amount.
periodNoPay period of amount.
currencyNo3-letter currency, e.g. INR.
locationNoOffer location.
offerTextNoPasted offer-letter text (optional).
experienceLevelNoOptional level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value beyond those annotations by disclosing what the output contains: a market percentile, the components that matter, an India in-hand estimate for INR, and negotiation advice. It does not state limits, such as how missing data is handled, which keeps it from a 5.

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 four short sentences, front-loaded with the purpose and followed by input modes and output contents, with no filler. The telegraphic phrasing ('what components matter', 'Needs a role.') is compact but slightly clipped and less explicit than plain prose would be.

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?

The tool has seven parameters, no output schema, and no nesting; the description covers the input modes and the shape of the result, which is enough for an agent to call it correctly. Minor gaps remain, such as defaults for currency or location and behavior when the role is ambiguous, but these do not block correct use.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema. It ties 'amount' to the required companion fields ('+currency, +period') and presents 'offerText' as an alternative input path, while the schema alone labels it merely optional. It also flags role as effectively required even though the schema marks no parameters as required.

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 first sentence names a specific verb and resource ('Compare a job offer with the market and get negotiation advice'), which clearly separates this tool's intent from salary calculators or research tools. It stops short of naming any sibling explicitly, so it lands just below the top of the scale.

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

Usage Guidelines3/5

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

'Accepts either an amount (+currency, +period) or pasted offer-letter text' and 'Needs a role' tell the agent how to invoke the tool, which is useful input routing. However, there is no explicit guidance about when to prefer salary_analysis, salary_calculator, or salary_research instead, so the guidance is implied rather than comparative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.