Skip to main content
Glama
Sign In

Usajobs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Job

get_job
Read-onlyIdempotent

Fetch a single announcement by USAJOBS announcement number.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "announcement_number": "AF-DHA-2024-12345"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
announcement_numberYesUSAJOBS announcement number (e.g. "AF-DHA-2024-12345")

Output Schema

NameRequiredDescriptionDefault
JobDataNoArray containing the matching job posting
SearchResultNoSearch result metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "announcement_number": "AF-DHA-2024-12345"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Single job posting result from USAJOBS",
+  "properties": {
+    "JobData": {
+      "description": "Array containing the matching job posting",
+      "items": {
+        "description": "Individual job posting with full details",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "SearchResult": {
+      "description": "Search result metadata",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already disclose the safety profile, so the description doesn't need to repeat it. However, the description adds no additional behavioral context beyond what the schema and annotations provide. This is acceptable but not enhanced.

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 a single, front-loaded sentence with no wasted words. It immediately states the action, the resource, and the unique identifier, making it highly concise and well-structured.

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

Completeness5/5

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

For a simple lookup tool with one parameter, full schema description, an output schema, and rich annotations, the description is sufficient. It doesn't need to explain return values or safety because those are covered by structured data.

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 schema description coverage is 100%, so the parameter 'announcement_number' is already well-documented. The description adds minimal meaning beyond what the schema provides, just restating 'by announcement number.' Baseline 3 applies.

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?

The description uses a specific verb ('Fetch') and resource ('a single announcement') with a clear identifier ('by USAJOBS announcement number'). This clearly distinguishes it from sibling tools like list_agencies or search, which serve different purposes.

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?

The description implies the usage context: you would use this tool when you have a specific announcement number and need the corresponding announcement. While it doesn't explicitly mention alternatives or exclusions, the context is clear enough for a get-by-ID tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Usajobs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources