Skip to main content
Glama

BlueTeamJobs

Get a job

get_job
Read-onlyIdempotent

Details of one job: pay, location, clearance, certifications, skills and a short excerpt.

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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe 6-character job id, or a blueteamjobs.com job URL.

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing the content of the response (pay, location, clearance, certifications, skills, excerpt), which matters because there is no output schema. It omits failure behavior for an unknown or expired id.

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?

One front-loaded sentence with no filler; the returned-field list is compact. It is appropriately sized, though it spends its words on return contents rather than usage routing.

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?

For a simple read-only single-record tool with a fully documented parameter, covered annotations, and no output schema, listing the returned fields makes the definition nearly self-sufficient. Only lookup-failure and id-provenance guidance are missing.

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 100%, and the schema itself explains that the id may be a 6-character id or a blueteamjobs.com URL. The description adds nothing about the parameter, so the baseline 3 for a fully documented single parameter is correct.

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?

States a specific verb and resource ('Details of one job') and enumerates the fields returned, so the agent knows this is a single-record detail fetch rather than a search. It does not explicitly name how it differs from siblings like latest_jobs or search_jobs, which keeps it from 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 Guidelines2/5

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

There is no explicit when-to-use, no prerequisite (e.g. 'requires an id from search_jobs'), and no mention of alternatives for list-style retrieval. The singular 'one job' only weakly implies the lookup-by-id case versus the sibling search tools.

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