Skip to main content
Glama

BlueTeamJobs

Blue team salary statistics

get_salary_stats
Read-onlyIdempotent

Pay percentiles (USD a year) from salaries published in BlueTeamJobs postings over the last 12 months, by role, US state, seniority or work arrangement. Needs at least 3 postings with pay.

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": "get_salary_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoRole slug or name. Omit for all blue team roles.
stateNoUS state name, code or slug, e.g. "Texas", "TX".
remoteNo
seniorityNo

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 declare this as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context: the data source, 12-month window, annual USD basis, and the requirement of at least 3 postings with pay before results are available.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the main purpose and then the sample-size constraint. It is dense with relevant information and has no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is read-only and has clear input constraints, but there is no output schema and the description does not specify which percentiles are returned or the response shape. For a statistics tool, that leaves a meaningful gap in what the agent should expect back.

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 description maps the four parameters to the dimensions role, US state, seniority, and work arrangement, which adds some meaning beyond the schema, especially clarifying that remote refers to work arrangement. With only 50% schema description coverage, it could have explained the enum values or omission behavior more fully, so this is adequate but not rich.

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 resource and computation: pay percentiles from BlueTeamJobs postings over the last 12 months, sliced by role, state, seniority, or work arrangement. It clearly distinguishes this from the sibling job-listing tools by being a salary aggregation tool, though it does not explicitly name alternatives.

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?

The scope is clear: salary percentiles from the last 12 months of postings, with a minimum sample of 3 paid postings. However, it does not explicitly say when to use this instead of search_jobs or latest_jobs, nor does it describe exclusions or edge-case behavior beyond the sample threshold.

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.

Resources