Skip to main content
Glama

Search occupations by title

search_occupations
Read-onlyIdempotent

Occupations whose title matches, best first. Each result carries its SOC code, its PERM record and the slug that the get endpoint takes. Example: {"q":"software"}.

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

Input Schema

NameRequiredDescriptionDefault
qYes2 to 120 characters of the title. Example: software.
limitNoResults to return, 1 to 100. 10 when left out. Example: 25.

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds real behavioral value with 'best first' relevance ranking and the shape of each result (SOC code, PERM record, slug), though the latter largely restates what the output schema already provides.

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?

Three short sentences, front-loaded with the purpose and ordering, then result contents, then an example. Little waste, though the result-contents sentence overlaps with the output schema.

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?

With an output schema present and full parameter coverage, the description only needs to establish purpose and ordering, which it does. Minor gaps remain around empty-result behaviour and whether matching is exact or partial.

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%, with both q and limit fully documented including bounds and the default of 10, so the baseline is 3. The inline example {"q":"software"} duplicates the schema's own example and adds no new meaning about matching behaviour (prefix, substring, or fuzzy).

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 names the resource (occupations), the matching field (title), and the ordering ('best first'), which is enough to distinguish it from get_occupation, which takes the returned slug. It never names get_occupation directly, only 'the get endpoint', so the sibling differentiation is implied rather than explicit.

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 closing sentence implies a two-step workflow: search here, then fetch with the get endpoint using the returned slug. There is no explicit statement of when to prefer this over search_employers, lookup_soc, or lookup_employer, and no guidance on what to do when no match is returned.

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.