Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

多标准绩点换算对照

gpa-multi

多标准绩点换算对照:绩点到底怎么算?常见4.0制、线性4.0、5.0制、百分制加权一次算给你对照,避免各校规则不同算错。填每门课成绩和学分即可。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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-multi"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the result is deterministic and comes with a stated basis ('返回确定性计算结果与依据') and that input is per-course score plus credit. It says nothing about what happens with out-of-range scores, missing credits, or the shape of the returned comparison table, which is a real gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded and the scales are enumerated clearly, but the rhetorical '绩点到底怎么算?' and the generic closing about regulation wording are filler that dilutes the signal.

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 one-parameter deterministic calculator with no output schema, the description covers the scales computed, the input it needs, and that the answer includes a stated basis — enough for an agent to call it correctly. Only the exact output layout is left unspecified, which is minor at this complexity.

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% and the single items array is already documented with an example object, so the schema does the heavy lifting. The description's '填每门课成绩和学分即可' confirms the same fields but adds no constraints, ranges, or credit-weighting rules beyond the schema.

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 states a specific operation — computing a GPA comparison across 4.0, linear 4.0, 5.0, and weighted percentage scales — and lists the scales covered, so an agent knows exactly what it produces. It does not differentiate itself from the sibling gpa-convert, so the agent must guess which of the two to pick.

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

Usage Guidelines3/5

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

The only usage cue is '适用场景:模型算数不稳、法规口径易错时' (use when model arithmetic is unreliable), which is a generic motivation rather than a condition that distinguishes this from gpa-convert. There is no when-not guidance and no named alternative.

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