Skip to main content
Glama

BlueTeamJobs

List job locations

list_locations
Read-onlyIdempotent

Places with open jobs (countries, US states and cities), most jobs first, plus the remote count.

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

Input Schema

NameRequiredDescriptionDefault
roleNoRole slug or name, e.g. "soc-analyst". See list_roles.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral detail beyond that: results are ordered by job count descending and include a remote count. It does not explain pagination or how limit affects the result set, keeping 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.

Conciseness5/5

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

A single compact sentence that front-loads the resource and includes only useful qualifying details. Nothing is redundant or wasted.

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?

For a simple read-only list tool with no output schema, the description covers the core result shape and ordering. However, it omits the role filter's effect and limit/pagination behavior, which are material for correct invocation.

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

Parameters2/5

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

The description mentions neither parameter. The schema documents role reasonably well (slug/name example and pointer to list_roles), but limit has no description beyond default/min/max. At 50% schema coverage, the description should compensate — especially by explaining that role filters the locations — but it does not.

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 identifies the resource (job locations: countries, US states, cities) and adds scope (open jobs), ordering (most jobs first), and an extra return element (remote count). It does not explicitly distinguish this tool from sibling search_jobs, which also returns jobs, so it stops short of a 5.

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 implied by 'Places with open jobs' — an agent can infer this is for discovering locations that have openings. However, there is no explicit when-to-use guidance, no comparison to search_jobs, and no mention of how the role filter should influence selection.

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