Skip to main content
Glama

getwork.dev

Search (natural language)

search
Read-onlyIdempotent

Job search from one plain-language request, e.g. 'remote senior Rust jobs in Europe over €120k, no crypto'. Use this when you have the user's words rather than filters; with filters in hand, search_jobs gives more control and richer results. Returns ids, titles and URLs, the total, filters (how the request was read, reusable with search_jobs) and broadened (filters dropped to find any results).

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe request in plain words: stack, level, place, remote, salary floor, things to avoid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"The request in plain words: stack, level, place, remote, salary floor, things to avoid."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-open-world), so the description focuses on what it alone can add: the returned fields (ids, titles, URLs, total), the `filters` echo showing how the request was interpreted, and the `broadened` flag revealing that filters may be silently dropped. That last point is a genuine behavioral caveat an agent needs. It stops short of covering result limits or ranking behavior.

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?

Three sentences, front-loaded with purpose, then the alternative, then the return contract. No filler and the example is embedded rather than given its own sentence.

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 one-parameter read tool with no output schema, the description supplies exactly what structured fields cannot: the return fields and the meaning of `broadened`. Nothing an agent needs in order to call it correctly or interpret its result is 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%, so the single `query` parameter is already documented with its own description covering stack, level, place, remote, salary and exclusions. The description's example reinforces that but adds little new semantics; the note about reusing `filters` with search_jobs is useful but concerns output, not the input parameter.

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?

States a specific verb and resource ('Job search from one plain-language request') and immediately contrasts it with the filter-based sibling search_jobs. The inline example ('remote senior Rust jobs in Europe over €120k, no crypto') makes the input shape unmistakable.

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?

Explicit routing rule: use this when you have the user's words, use search_jobs when you have filters, with the added rationale that filters give more control and richer results. Both the when and the when-not are stated.

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