Skip to main content
Glama

save_search_goal

Saves a user-defined job search goal, including primary resume, target directions, cities, exclusions, and source limits, so the workflow can use confirmed preferences without inventing them.

Instructions

记住用户明确指定的主简历、岗位方向、城市及排除项。sources 可省略,使用内置官网;不要擅自填写偏好。

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": {
      "resumeId": "<resumeId>",
      "directions": "<directions>"
    },
    "name": "save_search_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
citiesNo
excludeNo
sourcesNo
resumeIdYes
directionsYes
skipAppliedCompaniesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, closed-world write, so the safety profile is covered. The description adds meaningful behavior context - that sources default to built-in official sites and that the agent must not invent preferences - but stays silent on overwrite/merge behavior on repeat calls and on what limit and skipAppliedCompanies actually change.

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 core intent, and the sources default is stated immediately after. No filler, though the extreme terseness leaves the second half doing too little work for a seven-parameter 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?

For a seven-parameter write tool with zero schema descriptions and no output schema, the description covers the required fields and the sources default but omits two parameters and any statement of the resulting effect. It is workable but not sufficient on its own.

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%, so the description carries the burden. It maps five parameters to plain-language meaning (resumeId as primary resume, directions, cities, exclude, sources with a default rule), but leaves limit and skipAppliedCompanies entirely unexplained and gives no format expectations for the ones it does mention.

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 names a concrete resource set - primary resume, job directions, cities, exclusions - with the implicit verb of persisting the user's search goal, matching the tool name save_search_goal. An agent can tell what is being stored, but it is not explicitly distinguished from sibling goal_candidates or save_resume_version.

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?

There is implicit guidance that this should only be used for preferences the user explicitly stated ("用户明确指定的"), plus a rule for the sources field to fall back to built-in sites. However, no alternative tool is named for the case where the user has not stated preferences, so the agent must infer the boundary itself.

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