分页获取标签列表，用于在已知标签分组 ID 时列出该分组下的标签，并为客户搜索或历史会话搜索提供 tag_id。page 从 1 开始；page_size 最大 20。前置：可先调用 zhini_list_tag_groups 获取分组；如果用户只提供标签中文名，优先调用 zhini_search_tags 解析 tag_id。后续：拿到 tag_id 后可调用 zhini_search_customers 或 zhini_search_sessions。
ConnectorNo auth
593,574 tools. Updated 2026-09-20 19:40
"JavaScript逆向工程技术与方法" matching MCP tools:
- 搜索客户通讯录，用于根据客户名、手机号、微信号、客服、负责人、明确标签、渠道、性别、联系人类型或时间范围完整召回符合条件的客户 UID。用户只要求查询当天或某个时间范围内咨询过的客户时，默认查询当前授权账号关联的所有渠道范围，不代表当前调用客服本人接待或回复过；除非用户明确说“我处理过、我接待过、我回复过、归属于我”或指定某客服/渠道，否则不要自动传 kfid、pic_kfids 或 channel_id。用户要求查询某天或某段时间内的全部用户、包括会话已经结束/关闭的用户时，应使用本工具分页查询，不能用 zhini_list_active_sessions 代替。重要边界：自然语言中的“XXX 用户/客户”默认是业务语义或筛选条件，不应自动转换为 tag_id。可由名称、时间、渠道、客服等结构化字段表达的条件直接使用本工具；必须根据聊天内容判断的条件，应结合 zhini_search_sessions 和 zhini_fetch_messages 识别。只有用户明确要求某标签或上下文已有 tag_id 时才按标签筛选，且 tag_id 只覆盖已标注客户。用户给客户姓名/手机号/微信号时先用本工具召回候选客户；如果匹配多个客户，应让用户确认。用户明确给出标签名、渠道名、客服名时，应先分别调用 zhini_search_tags、zhini_list_channels、zhini_list_kefu 解析 ID。禁止空条件拉全量；page 从 0 开始；page_size 最大 20。后续：拿到 uid 后通常调用 zhini_get_customer_profile 或 zhini_fetch_messages。ConnectorNo auth
- Runs calculate_payslip for many employees in one call and returns the run totals: gross, employee deductions, net, and employer cost. Reach for this the moment more than two or three people are in play. A monthly payroll is not a sequence of unrelated questions — the employer share, the totals and the run id only mean anything across the whole run. Asking one employee at a time gives no total and no way to tell a retry from a second run. Put anything shared in defaults (prefecture, business_type, column) and let each row carry only what differs, which is usually pay and age. A row that cannot be computed comes back in errors with its index and id while the rest of the run completes — do not discard a whole payroll over one bad row. The reply carries a run_id derived from the route and the exact input, so sending the same payroll twice gives the same id. Nothing is stored, so a retry cannot double-count.ConnectorNo auth
- Runs the annual 定時決定 for a whole payroll in one call, and reports which employees moved grade. 健康保険法第41条 puts every insured employee on the same schedule — the average of April, May and June pay, over the months with at least seventeen payment-basis days, applied from September to the following August. So June is the one month of the year when an office decides its entire payroll at once, and asking about one employee at a time is the wrong shape for the task. Reach for this the moment more than a couple of employees are in play. Each row returns the same judgement as decide_regular_remuneration, plus whether that person changed grade, which is what decides how much filing there is. Pass previous_remuneration to get that comparison; without it the answer is null rather than false, because "no grade to compare" and "did not move" are different facts. Pass acquired_on, left_on or revision_month and each row also says whether that employee is filed at all. 健康保険法第41条 leaves out anyone insured between 1 June and 1 July, anyone gone before the 1 July reference date, and anyone revised from July to September. The run totals to_file and not_required, which is the number of forms rather than the number of employees. A row that cannot be decided is returned in errors with its index and id, and the rest of the run still completes — do not discard a whole run over one bad row.ConnectorNo auth
- What one employee costs an employer over a year, bonuses included. Reach for this rather than multiplying a payslip by twelve, because the two do not agree once a bonus is paid. 健康保険法第45条 caps the standard bonus cumulatively across the year — 5,730,000 from 1 April to 31 March — so the same bonus costs a different amount depending on where it falls, and once the year is used up later bonuses carry no health premium. 厚生年金保険法第24条の4 caps at 1,500,000 per payment with no yearly total, so pension keeps charging where health has stopped. Pass bonuses in the order they are paid: the health allowance fills from the first one. Each row comes back with what was counted, whether it was cut, and how much of the year remains, so the answer can be explained rather than just quoted. Income tax here is the monthly figure times twelve. Bonus withholding is a separate calculation (calculate_bonus with include_tax) and the year-end adjustment is a separate tool (calculate_year_end_adjustment) — say so rather than presenting this as take-home pay for the year.ConnectorNo auth
- Decides whether someone is covered by health and pension insurance, and on which payment-basis day count their annual determination runs. Call this before decide_regular_remuneration or judge_monthly_revision whenever the person is anything other than plainly full-time. Those tools take a worker_type, and guessing it changes a real number: the determination counts months of seventeen payment-basis days for an ordinary employee and eleven for a 短時間労働者. Get the classification wrong and the answer is wrong with no sign of it. 健康保険法第3条第1項第9号 covers anyone whose weekly hours and monthly days reach three-quarters of a comparable full-time worker. Below that, four further tests decide it: twenty hours a week, 88,000 yen a month, not a student, and a workplace of at least fifty-one insured people. The engagement must also be expected to run past two months. The 88,000 figure leaves out overtime, bonuses, commuting and family allowances. Folding those in is the usual route to a wrong answer, so ask for 所定内賃金 specifically rather than total pay. What counts as a comparable full-time worker, and whether someone is a student for this purpose, are facts about the workplace and the person. Ask rather than assume; the tool applies the tests to what you pass and names any it could not evaluate.ConnectorNo auth
Matching MCP Servers
- AlicenseNot gradedqualityCmaintenance面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills，涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询，并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。MIT No Attribution
- AlicenseAqualityCmaintenanceEnables clients to access 21 cloud-hosted financial tools via a token-authenticated forwarding layer that relays tool calls to the Silkj E-Investment skill gateway. Supports stdio, Streamable HTTP, and hosted deployment modes without embedding any financial algorithms locally.211MIT
Matching MCP Connectors
连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服的客户资料、会话与聊天记录，供AI查询分析。
斯特丹STERDAN天猫旗舰店产品咨询MCP Server。洛阳30年源头工厂，高端钢制办公家具，1374个SKU，涵盖保密柜、更衣柜、公寓床、货架、快递柜。BIFMA认证，出口35+国家。8个工具：产品目录查询、场景推荐、认证资质、采购政策、维护指南等。
- Returns the full text of a Japanese statutory provision, as published by e-Gov. The judgement tools name the statute or notice their answer rests on, but not its words. Use this to quote the provision itself — a citation the reader can check beats a citation they have to take on trust, and Japanese payroll advice is routinely wrong in ways that only reading the article reveals. Only the provisions this API cites are bundled (about 28 across 8 laws); call it with no ref to list them. Abbreviations as practitioners write them (健保法43条, 厚年法81条の2, 徴収法11条), a missing 第, and paragraph-level references all resolve to the article. For anything outside this set, say so rather than reciting it from memory.ConnectorNo auth
- 获取标签分组，用于了解标签体系、解释标签归属，或在列出某分组标签前获取 tag_group_id。边界：只读字典工具，不新增、修改或删除标签分组。前置：无。后续：已知分组后可调用 zhini_list_tags；用户直接给标签名时通常优先调用 zhini_search_tags。ConnectorNo auth
- For work whose April-June happens to be its busiest or quietest quarter, where the ordinary calculation would fix a grade that is wrong for eleven months of the year. Available for 定時決定 (since April 2011) and 随時改定 (since October 2018). The 随時改定 figure is NOT a plain twelve-month average: it is the three-month average of FIXED pay plus the twelve-month average of NON-FIXED pay, so the two are supplied separately, and three distinct grade tests must all pass. Both routes need the employee's consent and require that the swing recurs every year for reasons inherent to the work — a one-off busy period does not qualify. Neither is something this tool can verify, so both are declared inputs and are echoed back in the response.ConnectorNo auth
- Works out how many days of paid leave someone has been granted, and whether the employer still owes the five days it must direct. 労働基準法第39条 grants ten working days once six months of service are complete and attendance reaches eighty per cent of all working days, then adds one, two, four, six, eight and ten days in the years that follow. The ceiling everyone quotes as twenty is not in the article: it is the ten of the first grant plus the ten added from the sixth year. Someone under thirty hours a week working four days or fewer takes a smaller table from 施行規則第24条の3. Thirty hours is where it turns — at or above it the ordinary grant applies no matter how few days are worked, and treating such a person as part-time under-grants them. Ask for both the weekly days and the weekly hours; one without the other cannot settle it. Where ten or more days are granted, 第39条第7項 requires the employer to fix the timing of five of them within the year, and days the employee took of their own accord count toward it. A grant lapses two years after it is made (第115条), so one year carries over. The attendance figure is a question about the workplace: leave for a work injury, maternity, childcare and paid leave already taken all count as attendance. Ask for a rate that has been worked out rather than dividing days present by days in the year. Without one the tool reports the eighty per cent test as not judged rather than assuming it passed.ConnectorNo auth
- Works out how much of a commuting allowance escapes income tax, and states the amount that still counts as remuneration for social insurance. These are two different bases, and that asymmetry is the part people get wrong. Social insurance counts a commuting allowance in full — it is 報酬 under 健康保険法第3条第5項 regardless of the tax treatment — while income tax is charged only on what exceeds the ceiling. So a 15,000 yen allowance on a 300,000 yen salary makes the standard-remuneration basis 315,000 and the taxable pay 300,000. Never answer with a single figure that is meant to serve both. The ceiling is 150,000 a month for public transport. For a car or bicycle it is set by one-way distance, with nothing exempt under two kilometres, and up to 5,000 more a month when the employee pays for parking. Using both adds them together, still capped at 150,000. Do not answer this from memory. The table moved twice in twelve months: a cabinet order promulgated 19 November 2025 raised every band over ten kilometres and applied retroactively to allowances payable from 1 April 2025, and 1 April 2026 added four bands above 65km along with the parking addition. Figures learnt before those dates are wrong, and wrong in a direction that under-states the exempt amount. Call with no arguments to read the current table and both revisions.ConnectorNo auth
- 获取当前授权客服账号所负责渠道下尚未关闭、尚未结束的当前会话队列。用于查看此刻的待接待、我的会话、同事会话、AI 会话状态，或从当前队列选定会话后读取消息/客户资料。重要边界：这是当前队列快照，不是历史查询；当天或更早已经由当前授权账号、其他客服结束/关闭的会话不会返回，不能用本工具汇总某天或某段时间内的全部用户、全部接待或完整会话。需要完整用户范围时调用 zhini_search_customers；需要已结束、已关闭或历史会话时调用 zhini_search_sessions，必要时再用 zhini_fetch_messages 按消息时间验证。范围：只返回当前授权账号负责渠道下的会话，不是全企业所有会话；我的会话全部返回，同事会话最多显示 250 个，排队中/等待接待会话最多显示 100 个，达到上限时摘要应提示可能被截断。前置：需要区分“我的会话/同事会话”时，先调用 zhini_get_current_kefu 获取当前 kfid。ConnectorNo auth
- 搜索历史会话，用于按客户名、消息关键词、消息发送时间范围、客服、渠道、明确标签、联系人类型召回包括已结束、已关闭会话在内的历史会话候选。用户只要求查询当天或某个时间范围内的对话、咨询记录时，默认查询当前授权账号关联的所有渠道范围，不代表当前调用客服本人接待或回复过；除非用户明确说“我处理过、我接待过、我回复过、归属于我”或指定某客服/渠道，否则不要自动传 kfid 或 channel_id。用户要求查询某天或某段时间内的全部接待、完整会话或已结束会话时，应使用本工具分页查询，不能只调用 zhini_list_active_sessions。自然语言中的“XXX 用户/客户”默认是业务语义；当 XXX 必须根据聊天判断时，使用 msg 按相关表达召回候选，再用 msg_stime 限定消息发送时间范围，最后用 zhini_fetch_messages 读取完整上下文并由模型分类，不要先把 XXX 当成标签名。只有用户明确提到标签或已有 tag_id 时，标签才作为筛选条件或补充信号。关键词命中只是召回信号，不等于最终分类。条件性限制：仅当 msg 非空时，关键词历史检索只支持最近半年内的记录；msg 未传或为空、仅使用其他筛选条件（包括 msg_stime）时不受这条关键词专属限制。重要时间语义：msg_stime 表示消息发送时间范围，用于筛选时间段内包含消息的会话，不表示对话开启时间；旧字段 stime 已移除，不要传入。禁止空条件拉全量；page 从 0 开始；本工具不接收数量参数，底层查询默认每次返回 30 条，MCP 可全部展示给模型。ConnectorNo auth
- 获取当前调用者的客服 ID，即 kfid。用于在调用 zhini_list_active_sessions 前识别当前会话列表中哪些是自己正在接待的会话，或在用户明确说“我处理过、我接待过、我回复过、归属于我”等第一人称归属条件时构造 kfid 筛选。重要边界：用户只要求查询当天或某个时间范围内的对话、咨询过的客户时，默认范围是当前授权账号关联的所有渠道，不表示当前调用客服本人处理过，不应调用本工具或自动附加当前 kfid。本工具只输出 kfid，不输出手机号、姓名、团队、企业或负责渠道等身份信息。ConnectorNo auth
- 按客户 UID 获取客户资料和标签，用于确认客户身份、来源、负责人、联系方式、备注和标签。适用于客服回复前、销售跟进前、复盘客户历史前。边界：只读查询，不修改客户资料、备注、负责人或标签。前置：如果用户只给姓名/手机号/微信号，先用 zhini_search_customers 找 uid；如果已经有 uid，直接调用本工具。后续：需要聊天上下文时调用 zhini_fetch_messages。ConnectorNo auth
- 读取聊天消息。支持按 sid 首次加载会话消息、按 mid 游标翻页、按 uid 查询某客户消息。适用于查看当前会话上下文、查看历史会话命中词前后文、按 UID 拉取某段时间内消息并总结诉求/投诉/售后问题。已知 uid/sid/mid 时直接调用本工具，不要先搜索。约束：sid、mid、uid 至少传一个；传 mid 时建议同时传 direction；按 uid 查询时 start_time/end_time 可选；size 最大 20。时间语义：start_time/end_time 是消息发生时间过滤，不是会话开启时间。ConnectorNo auth
- 查询正和金库实时状态：NAV（净值）、金库 USDC 总资产、LOVE 总份额、累计溢价。只读，无需任何授权。传入 address 可同时查该地址的 LOVE/USDC 余额与浮盈。ConnectorNo auth
- 按关键词检索合规问答，返回最相关的若干条（含简要答案）。 Args: query: 检索词，如「转人工」「备案 登记」「知识库 切分」 top_k: 返回条数，默认 5ConnectorNo auth
- 落札・入札関連の士業 (司法書士・弁護士・不動産鑑定士・土地家屋調査士) を返す. Stages: post_acquisition (default — 落札後の所有権移転登記; 司法書士が法律上ほぼ必須), pre_bid (入札前の独立評価・権利確認), eviction (明渡し・強制執行), boundary_dispute (境界確定・分筆). Information-only — not a paid intermediary. Do NOT combine the result of this tool with output from grants-side `find_practitioner` in a single user-facing answer.ConnectorNo auth
- 依勞保老年年金法定公式（擇優兩式、提前/延後增減給每年 ±4%，上限 ±5 年（±20%））試算月領金額；年資未滿 15 年不符年金請領資格。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。ConnectorNo auth
- 列出目前支援的年度、資料版本與基本工資（月薪/時薪）。計算前可先用本工具確認有效的 year 值。ConnectorNo auth