Skip to main content
Glama

Kariaa Agents

Pay for a role in a place

estimate_pay
Read-only

Use when the person asks what a role pays, or whether an offer is fair, in a city or country. Returns what employers state, from recent postings that list pay: the typical range, how many postings it comes from, and examples with links. When there are too few, say so and research further yourself.

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": {
      "role": "<role>",
      "location": "<location>"
    },
    "name": "estimate_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
locationYes"City, Country" or a country

Output Schema

NameRequiredDescriptionDefault
periodNohour, month or year
currencyNoCurrency
examplesNoPostings with stated pay and links
postingsNoPostings the range comes from
typical_lowNo25th percentile of the low ends
typical_highNo75th percentile of the high ends

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, so the description focuses on what annotations cannot say: the data provenance ('what employers state, from recent postings that list pay'), the sample-size signal ('how many postings it comes from'), and the important limitation that thin data means the agent must research further. That is genuine behavioral context beyond the structured fields.

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?

Three sentences, front-loaded with the trigger condition, no filler. The enumeration of return contents is slightly redundant given an output schema exists, and 'research further yourself' is loose phrasing, but nothing is wasted.

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?

With an output schema present the description need not detail return values, and it correctly concentrates on when to call, data provenance, and the low-data caveat. The only gap is the undocumented role parameter, which leaves an agent unsure what string form produces good results.

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 50% — location is documented as '"City, Country" or a country' while role is bare. The description reinforces location granularity ('in a city or country') but adds nothing about role formatting (job title vs. occupation) or about how location specificity affects result quality, so it only partially compensates.

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 specific verb and resource ('what a role pays', 'whether an offer is fair') scoped to 'a city or country', and describes the returned artifact: typical range, posting count, and linked examples. An agent can distinguish this from search_jobs or get_job, which return listings rather than an aggregated pay estimate.

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?

'Use when the person asks what a role pays, or whether an offer is fair' gives a concrete trigger condition, and the closing sentence gives handling guidance for sparse results. It stops short of naming an explicit alternative (e.g. search_jobs) or a when-not condition, so it is clear but not exhaustive.

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.