Skip to main content
Glama
619,926 tools. Updated 2026-09-28 20:53

"爬取Wiki、语雀等帮助中心内容的工具或方法" matching MCP tools:

  • 判断一项 AI 服务要办哪些手续(备案/安全评估/标识),逐条给出法规依据。 Args: public_facing: 是否面向中国境内公众提供服务(仅内部使用请传 false) generates_content: 是否能生成文本/图片/音频/视频等内容 edits_face_or_voice: 是否提供人脸、人声等生物识别信息编辑功能(换脸、AI 配音、数字人) only_internal_use: 是否仅企业内部使用、不对外提供
    ConnectorNo auth
  • 按关键词检索中国 AI 合规条目,返回最相关的若干条(含结论与条文依据)。 Args: query: 检索词,如「AI 客服 备案」「AI 生成内容 标注」「训练数据 合法来源」「大数据杀熟」 top_k: 返回条数,默认 5
    ConnectorNo auth
  • 列出全部合规条目的标题清单。 Args: cluster: 可选,按集群过滤。可选值 genai-interim(生成式AI暂行办法) / ai-content-label(AI生成合成内容标识) / deep-synthesis(深度合成) / algo-recommendation(算法推荐与备案) / filing-practice(备案实操)
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    A
    quality
    C
    maintenance
    Enables 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.
    21
    1
    MIT

Matching MCP Connectors

  • 斯特丹STERDAN天猫旗舰店产品咨询MCP Server。洛阳30年源头工厂,高端钢制办公家具,1374个SKU,涵盖保密柜、更衣柜、公寓床、货架、快递柜。BIFMA认证,出口35+国家。8个工具:产品目录查询、场景推荐、认证资质、采购政策、维护指南等。

  • Japanese agriculture policy, subsidies and rice advance payments. 日本の農業政策・補助金・米の概算金

  • 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
  • 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
  • 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
  • 用自然语言描述需求(如"人形机器人髋部高扭矩电机")做语义召回,返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量(构建时预计算、零外发、零外部模型)在当前全量实体上生成,是兼容性判定之外的"发现"通道:当你不确定零件的确切型号或参数名时,用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索,并明确告知。
    ConnectorNo auth
  • 探测一个中文问题在信源池里的实际占位分布,并判断你的品牌/域名是否在池子里。 原理:AI 答案只能引用「已进入检索池」的来源。若目标问题下主流信源被平台型站点 (知乎/公众号转载站/百家号/CSDN 等)占满而你不在其中,再好的站内优化也不会被引用。 返回:结果域名分布、平台归类、是否命中你的品牌/域名、同题竞品域名清单、建议动作。 参数:question 用户真实会问的问题原话;brand 品牌词(如「合尘猫」);domain 你的域名(如 savantcat.cn)。
    ConnectorNo auth
  • 按五大核心指标 + 语义角色分权,计算 AI 搜索可见度并输出可自验的测量报告。 输入 samples 为 JSON 字符串: {"brand":"合尘猫","domain":"savantcat.cn","baseline_negative":3, "fact_points":["服务范围","交付周期","定价方式"], "samples":[{"question":"Q1","platform":"DeepSeek","run":1,"answer":"原文回答……", "role":"independent|joint|citation_only|none", "sentiment":"positive|neutral|negative", "facts":"accurate|partial|wrong|unverifiable", "facts_found":["服务范围"],"as_of":"2026-09-19"}]} 口径:每题建议多轮(同一问题重复 7-8 次);role 分级对应语义角色权重; 返回五大指标、语义角色加权分、逐题明细与「原文摘录」(便于客户自验)。 verify_citations=True 时会实测 AI 回答里引用的 URL 是否真的可访问(幻觉守卫); extract_claims=True 时会把回答中的数字声明单独列出并标记为未核验。
    ConnectorNo auth
  • 列出目前支援的年度、資料版本與基本工資(月薪/時薪)。計算前可先用本工具確認有效的 year 值。
    ConnectorNo auth
  • 获取参数口径规范:同一个 torque/speed 字段在不同厂商那里含义可能不同(库内 torque 出现 19 种口径、speed 37 种,甚至混入 Gbps 与 rad/s)。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单,用于判断两份参数表到底能不能直接比较。
    ConnectorNo auth
  • 对一组零部件(BOM,物料清单)做两两兼容性矩阵。输入已有条目 ID(可含开源贡献层 OSS-xxx),返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测;未声明维度记为无法判定,不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据,overall_compatible=null 表示"证据不足",不等于不兼容。
    ConnectorNo auth