Skip to main content
Glama
can4hou6joeng4

boss-agent-cli

by can4hou6joeng4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

boss_search

Search BOSS Zhipin job listings by keyword. Filter by city, salary, experience, education, and welfare to find matching roles.

Instructions

按关键词和筛选条件搜索 BOSS 直聘职位列表。支持城市、薪资、经验、学历、福利等多维度筛选。 [可用性: 可用性: roles=candidate; candidate_platforms=zhipin; recruiter_platforms=-]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo城市名称（如 北京、广州）
pageNo页码
sortNo排序方式relevance
queryYes搜索关键词（如 Golang、Python 后端）
salaryNo薪资范围（如 20-50K）
welfareNo福利筛选，逗号分隔 AND 逻辑（如 双休,五险一金）
educationNo学历要求（如 本科）
experienceNo经验要求（如 3-5年）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.1
  2. Removedv1.18.0
  3. Addedv1.17.0
  4. Removedv1.16.0
  5. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / sort
      Added value: +{
+  "default": "relevance",
+  "description": "排序方式",
+  "enum": [
+    "relevance",
+    "score"
+  ],
+  "type": "string"
+}
  6. First observedv1.11.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It says it searches but does not state that it is read-only, how pagination works despite a page param, result format, or rate limits. The availability line adds role scope but little else behavioral.

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 tight sentences with the verb and primary purpose front-loaded, followed by the filter summary. The availability tag has a duplicated '可用性: 可用性:' and adds minor noise, but overall it is efficient.

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 an 8-parameter search tool with no annotations and no output schema, the description covers purpose, filter dimensions, and audience, but omits result/pagination behavior and the relevance-vs-score sorting distinction. Adequate but with clear gaps.

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%, so every one of the 8 parameters is already documented with examples. The description adds only a high-level framing of filter dimensions (city, salary, experience, education, welfare), not syntax or semantics beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (搜索/search) and resource (BOSS 直聘职位列表) and enumerates the filter dimensions it supports. It is reasonably distinguishable from siblings like boss_detail or boss_recommend, though it never names an alternative to sharpen the boundary.

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?

No explicit when-to-use-vs-alternative guidance against the dozens of sibling tools. The availability tag (roles=candidate, recruiter_platforms=-) does imply the candidate-only audience, which is useful usage context, but there is no exclusion or routing logic.

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

Deploy Server

Other Tools