Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

加权成绩/综合分计算器

weighted-score

加权成绩/综合分计算器:平时分+期中+期末按权重算总评,或算保研综合分、奖学金评定分。填各项分数和权重,自动校验权重之和。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "parts": "<parts>"
    },
    "name": "weighted-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsYes分项数组:[{"name":"平时","score":90,"weight":0.3}, ...],权重和=1或100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose real behavior: weights are auto-validated (sum must be 1 or 100), the result is deterministic and returned with a rationale/依据. It stops short of describing what happens on validation failure or the exact response shape, so a modest gap remains.

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?

Purpose is front-loaded, then use cases, then the fallback rationale; every sentence adds something. The opening phrase duplicates the tool title, which is minor waste.

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 single-parameter, side-effect-free calculator with no output schema, the description covers input semantics, the weight-sum validation rule, and the nature of the return value (deterministic result plus basis). Only the precise output shape/units are left implicit, which is acceptable here.

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 coverage is 100% for the single `parts` parameter, and the description only restates that scores and weights are supplied per item and that weights must sum to 1 or 100 — information the schema already carries. Baseline 3 applies since the schema does the heavy lifting.

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?

Names a concrete operation (weighted total = 平时+期中+期末 by weight) plus named use cases (保研综合分, 奖学金评定分), so an agent knows exactly what it produces. It does not explicitly contrast itself with numeric siblings such as gpa-multi or gpa-convert, so the sibling-differentiation bar for a 5 is not fully met.

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?

Gives an explicit trigger condition: call it when model arithmetic is unreliable or regulatory/formula conventions are error-prone, and it must return a deterministic answer. It provides no when-not guidance or named alternative tool, which keeps it below a 5.

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