Skip to main content
Glama
Terranslayer

D&D 5e Tool Server

by Terranslayer

cr_to_xp

Converts a D&D 5e creature's challenge rating (CR) to its experience point (XP) value, accepting formats like '1/4' or '5'.

Instructions

挑战等级转经验值(接受 '1/4'、'5' 等)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

没有提供注释,因此描述需要承担行为透明度的负担。描述说明了它接受字符串形式的CR值(如'1/4'、'5'),但未说明返回格式、错误处理或是否处理所有CR范围。对于纯计算工具,没有副作用或权限要求,但缺乏细节限制了行为透明度。

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

Conciseness5/5

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

描述非常简洁,仅一句话,信息量饱满,直接以功能起始并给出参数示例。没有冗长内容,每个词语都承载信息,符合前端加载原则。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

该工具非常简单,仅有一个参数且无输出 schema。描述提供了转换功能和参数格式,但未说明返回值的具体形式(如数值、单位)或潜在限制(如是否包含整数CR的全部列表)。对于简单工具,描述可用但并未完全覆盖 agent 可能需要的所有上下文。

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?

输入参数的 schema 描述覆盖率为0%,而描述明确说明了参数'cr'的语义,指出它接受字符串形式的挑战等级(如'1/4'、'5'),并暗示了可接受的格式。这显著超越了原始 schema,有助于 agent 正确构造输入。

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

描述明确说明了功能:将挑战等级(CR)转换为经验值(XP),并给出了示例输入('1/4'、'5'),这表明了具体动词(转换)和资源(CR到XP)。它与其他兄弟工具(如encounter_budget、monsters_by_cr)有明显区分,agent 可以快速确定该工具的用途。

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?

描述隐含了使用场景(需要将CR转为经验值时),但没有提供何时不使用此工具的排除条件或替代方案。没有提到与相关工具(如encounter_budget)的区别,但考虑到功能简单,基本上下文是清晰的。

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