Usajobs

List Pay Grades

list_pay_grades

Read-onlyIdempotent

Return the USAJOBS reference list of pay plan codes (GS, FW, ES, etc.) and their descriptions; use pay plan codes with the pay_grade_low/pay_grade_high search filters.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`CodeList`	No
`DateGenerated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

removedOutput schema / properties / Code

Removed value: -{
-  "description": "List of pay grade codes",
-  "items": {
-    "properties": {
-      "CodeName": {
-        "description": "Pay grade name",
-        "type": "string"
-      },
-      "CodeValue": {
-        "description": "Pay grade code (GS, FW, etc.)",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / CodeList

Added value: +{
+  "items": {
+    "properties": {
+      "ValidValue": {
+        "items": {
+          "properties": {
+            "Code": {
+              "type": "string"
+            },
+            "IsDisabled": {
+              "type": "string"
+            },
+            "LastModified": {
+              "type": "string"
+            },
+            "Value": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / DateGenerated
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Pay grade/plan reference codes",
+  "properties": {
+    "Code": {
+      "description": "List of pay grade codes",
+      "items": {
+        "properties": {
+          "CodeName": {
+            "description": "Pay grade name",
+            "type": "string"
+          },
+          "CodeValue": {
+            "description": "Pay grade code (GS, FW, etc.)",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish this as a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false). The description adds real context beyond them by identifying the payload as a static reference/enumeration list of codes plus descriptions, which tells the agent this is lookup data rather than a mutable or filtered resource.

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 front-loaded sentence with no waste; the resource is stated first and the usage note follows after a semicolon.

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?

With an output schema present, the description needn't enumerate return fields. It covers what is returned and how to apply the codes, which is everything needed to select and call a zero-parameter lookup tool.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly implies no inputs are needed and instead explains how the returned codes feed other tools' filters.

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?

Specific verb and resource: 'Return the USAJOBS reference list of pay plan codes (GS, FW, ES, etc.) and their descriptions.' The examples of codes and the reference-list framing distinguish it from siblings like list_agencies and list_occupational_series.

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?

It states what the output is used for: 'use pay plan codes with the pay_grade_low/pay_grade_high search filters.' That gives a clear downstream context, but it names no alternative tool and no exclusion for when not to call it.

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

All Usajobs tools Inspect

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.