Skip to main content
Glama

getwork.dev

Similar jobs

similar_jobs
Read-onlyIdempotent

Active roles at any company that resemble a given job (title, stack and description overlap), leaving out the same role at other locations. Use it to widen a shortlist from one job the user liked. Returns compact JobSpecs like search_jobs.

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

Input Schema

NameRequiredDescriptionDefault
idYesId of the job to compare against.
limitNoHow many similar roles to return.

Output Schema

NameRequiredDescriptionDefault
jobsYes
similar_toYes
security_noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Id of the job to compare against."
    • addedInput schema / properties / limit / description
      Added value: +"How many similar roles to return."
  2. First observed

TDQS

A4/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 and repeatability are covered. The description adds real value beyond that with the similarity definition, the location-dedup rule, and a prediction of the return shape (compact JobSpecs like search_jobs). It does not, however, disclose how results are ranked or ordered by similarity, which is the main behavioral question for this kind of tool.

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 tight sentences with the core identification first, the usage trigger second, and the return preview last. No filler and nothing that merely restates the title.

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, the description doesn't need to enumerate return fields, and the "compact JobSpecs like search_jobs" pointer is a useful shorthand. The remaining gap is ranking or ordering of the similar roles, which matters when limit caps the result set.

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 description coverage is 100%, so both id and limit are already documented, giving a baseline of 3. The description adds modest meaning by explaining what "compare against" means in terms of overlap dimensions, but it says nothing about limit behavior or ordering that would go beyond the schema.

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 concrete resource (active roles across companies) and the exact matching criterion for similarity: title, stack, and description overlap. It also states a scoping exclusion (same role at other locations) and contrasts implicitly with search_jobs by framing itself as shortlist-widening, so an agent can pick it apart from the search siblings.

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?

"Use it to widen a shortlist from one job the user liked" gives a clear when-to-use trigger, and the exclusion of duplicate locations implies when results differ from a plain search. It stops short of naming a sibling or stating when not to use it, so a full 5 isn't warranted.

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