Skip to main content
Glama

goal_candidates

Read-only

Filters stored job postings by goal, excludes already submitted or pending duplicate applications, and returns supporting evidence plus missing information.

Instructions

按目标筛选资料库已有岗位,排除已提交及待核对的重复投递,返回证据与待补信息。

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": {
      "goalId": "<goalId>"
    },
    "name": "goal_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. Beyond that, the description adds real behavioral detail: a deduplication/exclusion rule (排除已提交及待核对的重复投递) and a statement of what is returned (证据与待补信息). It does not mention result limits or pagination, which keeps it from a 5.

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?

One sentence, front-loaded with the core action, then the exclusion rule, then the return contents. Each clause adds distinct information and there is no filler.

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 one required parameter, no output schema, and annotations covering the safety profile, the description covers the essential ground: what is filtered, what is excluded, and roughly what comes back. The remaining gap is the origin/format of goalId and any cap on result volume.

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 0% and the single parameter goalId carries no schema-level documentation. The description partially compensates by saying results are filtered '按目标', implying goalId is a goal identifier used as the filter key, but it does not say where a goalId comes from (e.g., save_search_goal) or its format.

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 gives a specific verb (筛选/filter) and a specific resource scope (资料库已有岗位 — jobs already in the library), plus the filter key (按目标/by goal). The phrase '已有岗位' implicitly separates it from discovery-type siblings like discover_jobs, but no sibling is named, so differentiation is inferential rather than explicit.

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 implied by the scope: this operates on jobs already in the library rather than new ones, and it excludes already-submitted or pending-verification duplicates. However, there is no explicit statement of when to call this instead of discover_jobs or application_history, and no prerequisites (e.g., needing a saved goal) are stated.

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