Skip to main content
Glama

OpeningsFirst

Similar jobs

similar_jobs
Read-only

Open jobs most similar in meaning to one job.

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

Input Schema

NameRequiredDescriptionDefault
limitNo1-25, default 10
job_idYesA job id from any list.
same_countryNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The tool has a 'readOnlyHint' annotation, which informs the agent it is safe to invoke. The description adds functional context (similarity search) but does not disclose complex behavioral constraints like API limits or specific data integrity rules beyond the schema.

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?

The definition uses a single, direct sentence that is maximally concise while still capturing the primary function of the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that it is a read-only operation (indicated by annotations) and provides a complete input schema, the description is sufficient for an agent to understand the operation and call it correctly without needing further information on return structure.

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?

The schema description coverage is 100%, making the description's role minimal. No additional semantic meaning or functional constraints are added regarding the parameters beyond what the input schema already details. Baseline score is appropriate.

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 clearly identifies the tool's purpose: finding jobs similar in meaning to a specified job. This distinguishes it from general search tools, although it does not explicitly name any similar siblings for comparison.

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

Usage Guidelines2/5

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

The description states what the tool does but offers no guidance on when an agent should choose this tool over alternatives like search_jobs or get_job. It provides no exclusionary criteria or conditional usage.

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