Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

出勤安全线(还能缺几次课)

attendance

出勤安全线(还能缺几次课):这学期还能缺几次课?按总课时、已缺课、学校最低出勤率,算出你的出勤安全线和还能缺的课时数,临界提前预警。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "total": "<total>",
      "attended": "<attended>",
      "absent": "<absent>",
      "minAttend": "<minAttend>"
    },
    "name": "attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
totalYes学期总课时
absentYes已缺勤课时
attendedYes已出勤课时
minAttendYes学校最低出勤率,0.75 或 75 均可(可选,默认0.75)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose useful traits: the result is deterministic, it returns the computed basis (依据) alongside the number, and it issues an early warning near the threshold. It does not describe the response shape, units, or what happens when minAttend is omitted despite being listed as required.

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?

The core question ('how many more classes can I miss?') is front-loaded and the calculation basis follows immediately. Mild waste exists: the title repeats the same phrase as the opening question, and '传入参数对象,返回确定性计算结果与依据' is generic boilerplate that could be tightened.

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?

For a four-parameter, pure-arithmetic tool with full schema coverage and no output schema, the description covers purpose, trigger condition, and output nature adequately. The remaining gap is the absence of any statement about edge cases such as already-failing attendance or inconsistent total vs. attended+absent inputs.

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 all four parameters are already documented with Chinese labels and the minAttend flexibility (0.75 or 75) is spelled out in the schema. The description only restates three of the inputs by name and adds no format, unit, or validation detail beyond what the schema provides, so baseline 3 applies.

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 specific computed output (attendance safety line and remaining allowable absences) and states its inputs: total class hours, hours already missed, and the school's minimum attendance rate. It is unmistakably a calculation tool and does not overlap with any sibling in the listed catalog, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger: call this when model arithmetic is unreliable or regulatory interpretations are error-prone. That is a clear when-to-use signal. It does not state exclusions or edge conditions (e.g., what to do if the student is already below the line), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources