Skip to main content
Glama

Quera job filter choices

qr_job_filters
Read-onlyIdempotent

List valid filter values for job and company searches, such as cities, industries, sizes, and popular tech codes; any tech code is accepted beyond the listed options.

Instructions

List the filter values qr_jobs and qr_companies accept: cities, industries, sizes, popular tech codes.

Any tech code works, not only these.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qr_job_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the enumerations are non-exhaustive, since any tech code is accepted beyond the listed set — a fact an agent could otherwise get wrong by treating the list as a closed enum.

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?

Two sentences, both earning their place: the first states scope and categories, the second removes the closed-enum misreading. No filler, no restatement of 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 no parameters and no output schema, the description carries little burden and covers the essentials: what is listed, for which tools, and that the list is not exhaustive. The only omission is any indication of the shape of the returned values (grouped by category vs. flat), which is minor for a lookup tool.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly adds no per-parameter detail and instead spends its words on what the returned value list covers.

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?

Specific verb (list) plus a precisely scoped resource (filter values accepted by qr_jobs and qr_companies), with the value categories named: cities, industries, sizes, tech codes. It explicitly ties itself to two named sibling tools, so an agent can distinguish it from the data-fetching siblings without opening the schema.

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?

It states the consumer tools whose arguments it resolves, which implies the when (call before filtering qr_jobs/qr_companies). It does not state exclusions or explain how it relates to the sibling qr_problem_filters, so the routing between the two filter tools is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.