Skip to main content
Glama

refine_shortlist

Read-onlyIdempotent

Filter saved job listings by location, workplace, companies, include/exclude terms, and candidate fit, then optionally rank matches to identify relevant roles.

Instructions

Filter saved jobs and optionally rank them. No paid call; unsupported or unknown attributes must not be guessed.

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": {
      "search_id": "<search_id>",
      "filters": "<filters>"
    },
    "name": "refine_shortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filtersYes
candidateNo
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context in 'No paid call' and the constraint that unsupported or unknown attributes must not be guessed, but it says nothing about how filtering and ranking interact or whether results are limited/capped.

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?

Two short sentences, front-loaded with the primary action, with no redundant restating of the name or title. The second sentence is terse to the point of being cryptic, but nothing is wasted.

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

Completeness2/5

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

The tool has a complex nested input schema with zero parameter documentation, no output schema, and a sibling that overlaps on ranking. Given that complexity, a two-sentence description is well short of what an agent needs to fill in filters and candidate correctly or predict the return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has four parameters including two deeply nested objects (filters and candidate) with 0% description coverage. The description never mentions search_id, limit, filters, or candidate, so an agent gets no guidance on what the nested filter fields mean or how the candidate profile influences ranking. The clause about not guessing unknown attributes gestures at filter validation but does not document any parameter.

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 (filter saved jobs) plus a secondary capability (optionally rank them), which is enough for an agent to identify the operation. It stops short of distinguishing this tool from the sibling rank_jobs or explaining how filtering relates to get_saved_results.

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?

Usage is only implied: the tool operates on saved jobs and can rank them, and 'No paid call' hints at a free/local operation versus presumably paid search tools. There is no explicit statement of when to use this instead of rank_jobs or get_saved_results, and no prerequisites are given.

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