Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

GPA 绩点换算(四点制)

gpa-convert

GPA 绩点换算(四点制):按课程分数与学分算四点制 GPA,附换算规则与"各校规则不同"提示。留学申请、奖学金自评快速估算。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "items": "<items>"
    },
    "name": "gpa-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes课程数组:[{score, credit}, ...]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It discloses that the output is deterministic, that it includes the reasoning basis and the conversion rules, and that it warns that rules differ by school. However, it says nothing about how invalid scores or credits are handled, what the output shape is, or what the failure modes are, leaving real gaps for a computation tool with no annotation coverage.

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 definition is short and front-loads the computation and its caveat before the usage contexts. There is mild redundancy: the use case is stated once as 'study abroad / scholarship self-assessment' and again as 'use when model arithmetic is unreliable', and the sentence '传入参数对象,返回确定性计算结果与依据' is somewhat boilerplate. It is still efficient overall.

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 tool with no annotations and no output schema, the description is largely sufficient: it states what is computed, what accompanies the result (rules and a disclaimer), and when to call it. The remaining shortfall is that the return structure is only described in general terms, but 'deterministic calculation result plus basis' plus the rules and disclaimer hint is adequate at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has only one parameter with 100% description coverage, so the baseline would be 3. The description nevertheless adds genuine meaning beyond the terse schema: it explains that the GPA is computed from course scores AND credit weights, clarifying the roles of score and credit inside the items array. It still omits the score-to-grade-point mapping, which is deferred to the returned rules.

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 gives a specific verb and resource: it converts course scores plus credits into a 4.0-scale GPA, and it also attaches the conversion rules and a caveat that each school's rules differ. That is far more concrete than a restatement of the title, and its domain is clearly distinct from siblings such as bmi-check or gross-margin. It does not explicitly name a sibling tool that covers an alternative case, which keeps it just short of a 5.

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?

The description gives concrete usage contexts: quick estimates for study-abroad applications and scholarship self-assessment, and situations where a model's arithmetic is unreliable or the regulatory basis is error-prone, so the agent should call this tool for an accurate answer. It does not state when NOT to use the tool, nor does it point to an alternative, but the positive guidance is clear and actionable.

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