Skip to main content
Glama

Usajobs

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it returns top-N tools with names, descriptions, full input schemas, and curated examples, and emphasizes results are ready to call directly with no second schema lookup needed. This gives useful behavioral context beyond the annotations.

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?

Front-loaded with a clear verb phrase ('Find tools by describing the data or task'), then usage guidance, then return format. The domain list is long but reinforces scope. It's slightly verbose but well-organized and every sentence serves a purpose.

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 no output schema, the description compensates by describing the return value (names, descriptions, schemas, curated examples) and provides strong usage context. It doesn't cover failure modes or edge cases, but for a read-only discovery tool with full annotations, it is adequate.

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 descriptions for query, limit, and aliases. The description adds no new parameter semantics beyond example queries and the 'top-N' concept, which the schema already explains (default 20, max 50). The description's domain list helps formulate queries but doesn't add parameter-level detail.

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 states 'Find tools by describing the data or task' and enumerates supported domains (SEC filings, FDA drugs, etc.), clearly framing it as tool discovery. It distinguishes from data-search siblings like 'search' or 'search_within' by emphasizing discovering available tools rather than querying data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly instructs when to use: 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This provides clear context and differentiates from alternatives like direct search tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all handle factual queries, and the Polymarket suite (polymarket_arbitrage, polymarket_edges, bet_research) has fuzzy boundaries. Even with long descriptions, agents will struggle to choose correctly among these clusters.

Naming Consistency3/5

Naming is snake_case but inconsistent in style: some tools are verb-led (get_job, list_agencies, validate_claim), others are noun-led (polymarket_edges, ai_visibility_check, recent_changes). The pattern is predictable only in that everything is snake_case, but the verb/noun order varies.

Tool Count2/5

36 tools is excessive for a server nominally called 'Usajobs'; the bulk of tools (Pipeworx, Polymarket, memory) are unrelated to the server's apparent purpose. The count feels like a bundled platform rather than a focused tool set.

Completeness4/5

For the USAJOBS subset, coverage is solid: search, get_job, and reference lists for agencies/occupational series/pay grades cover the read-only domain. However, the broader tool surface is sprawling and lacks a clear organizational principle, making completeness hard to assess; major data lookup features are present but via meta-tools rather than dedicated ones.

Resources