Skip to main content
Glama

atlas_get_candidate_search

Read-onlyIdempotent

One past candidate search: its candidates' labels and LinkedIn profiles and, for a Spotter email search, Spotter's reply with names and summaries (names are not kept for searches made here). Free.

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>"
    },
    "name": "atlas_get_candidate_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYesFrom atlas_list_candidate_searches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search_id / description
      Previous value: -"search_id from atlas_list_candidate_searches or atlas_search_candidates"New value: +"From atlas_list_candidate_searches"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for extra context: it discloses that names are not retained for searches made here, and that the call is 'Free' — a cost signal not present in the annotations. It does not describe failure modes for a missing or foreign search_id.

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?

One sentence, front-loaded with the resource and its payload, with the Spotter-specific case and the free/name-retention caveats packed in. The nested parentheses and repeated 'Spotter' phrasing make it slightly dense, 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?

With no output schema, the description carries the return-value burden and does so reasonably: labels, LinkedIn profiles, and the Spotter reply shape. Only edge cases (no results, expired search, permission limits) are left unaddressed, which is minor for a single-parameter read tool.

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% and the single parameter already documents its source ('From atlas_list_candidate_searches'). The description adds nothing about search_id format, validity, or scoping, so the baseline 3 applies.

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 it returns a single past candidate search along with its candidates' labels and LinkedIn profiles, and adds what a Spotter email search returns. The singular scope ('One past candidate search') distinguishes it from the list-oriented sibling, though the verb itself is implicit rather than stated.

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: 'One past candidate search' signals single-record retrieval versus listing, and the schema's 'From atlas_list_candidate_searches' points to the discovery path. There is no explicit statement of when to prefer this over atlas_get_candidate or when not to call it.

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