Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Research salaries

salary_research
Read-onlyIdempotent

Salary research for a role from published Jobiba salaries: market percentiles (p10-p90) with sample size and confidence, 3-year trend, pay by experience level, skills associated with higher pay, best-paying cities, live jobs that publish pay, and plain-language observations. Returns an explicit no-data result when samples are too few.

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>"
    },
    "name": "salary_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole title, e.g. 'Product Manager'.
locationNoCity or country (optional).
experienceLevelNoOptional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the data provenance ('published Jobiba salaries') and, importantly, the failure behavior: 'Returns an explicit no-data result when samples are too few.' That no-data contract is a genuine behavioral disclosure an agent needs for planning. It stops short of stating freshness, caching, or latency, so not 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?

Purpose and data source are front-loaded in the first clause, and the second sentence delivers the no-data contract. The middle enumeration of seven output types is long but each item is informative rather than filler. Slightly dense, 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?

There is no output schema, so the description must carry return-value information — and it does, listing percentiles, sample size, confidence, trend, skills, cities, and live jobs, plus the empty-result case. For a three-parameter read tool this is close to complete; only the location semantics and role-matching behavior remain underspecified.

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 description coverage is 100%, so the schema already documents all three parameters including the enum values. The description adds only indirect meaning — 'best-paying cities' hints at what location does and 'pay by experience level' hints at the experienceLevel parameter — but it never says whether location filters, scopes, or compares, nor how a role string is matched. Baseline 3 applies when the schema carries the parameter burden.

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 states a specific verb and resource ('Salary research for a role') and enumerates concrete outputs — percentiles, trend, experience-level pay, cities, live jobs. However, it never distinguishes itself from the sibling tools salary_analysis and salary_calculator, so an agent cannot tell from this text alone which of the three salary tools to pick.

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?

Usage is only implied: an agent can infer 'call this when you want market pay data for a role.' There is no explicit when-to-use statement, no exclusions, and no routing to salary_analysis or salary_calculator, which is exactly where guidance would matter most given the sibling set.

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.