Skip to main content
Glama

Find similar jobs

find_similar_jobs
Read-onlyIdempotent

Open jobs like one a search returned: the same role, in the same country, remote when it is remote, from employers' own careers sites first. The job itself is left out.

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": "find_similar_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA job's id, as a search result gives it (8 letters and digits).
limitNoHow many jobs, 1 to 19 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so safety is covered. The description adds real behavioral context beyond that: employers' own careers sites are preferred first, and the seed job is excluded from results. It does not describe ranking beyond that ordering or how 'similar' is computed.

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?

A single front-loaded sentence with dense, purposeful clauses and no filler. It is slightly clause-heavy and could be split for readability, but nothing is wasted.

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?

For a two-parameter read-only lookup with no output schema and full schema coverage, the description covers what the results will be (open jobs, same role/country, remote parity, careers-site preference) and the exclusion of the seed job. Only the result ordering guarantee beyond the careers-site preference is unstated.

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?

Schema coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds meaning where the schema is thin: the id is characterized as coming from a search result, which tells an agent the expected provenance and the exclusion semantics of that id.

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 states a specific verb and resource: it returns open jobs similar to one a search returned. It also encodes the matching dimensions (same role, same country, remote parity) and notes the input job is excluded, which distinguishes it from get_job or search_jobs.

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 phrase 'like one a search returned' implies it should be called after a search result, and 'the job itself is left out' implies when-not-to-expect. However, it never names search_jobs or get_job as the alternative path, and no explicit prerequisite or exclusion guidance is given.

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