Skip to main content
Glama
rc-ventura

Fantasy Gamebook Engine

by rc-ventura

create_character

Roll a new hero's attributes and save a living character sheet for gameplay.

Instructions

Roll a new hero's attributes and persist a living character sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
goldNo
luckYes
nameYes
aliveNo
skillYes
staminaYes
inventoryNo
conditionsNo
provisionsNo
Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It mentions rolling attributes and persisting but omits details like randomness, persistence mechanism, permissions, or side effects such as overwriting existing data.

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 description is a single sentence, which is concise. However, it lacks structure and important details, making it somewhat under specified rather than efficiently informative.

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

Completeness2/5

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

Given the simple schema (one parameter) and presence of an output schema, the description should at least hint at the output or necessary context. It does not mention what is returned or any state dependencies, leaving gaps for an AI agent.

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

Parameters1/5

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

The parameter 'name' has no schema description (0% coverage), and the description does not explain its role, format, or constraints. The sentence implies creation but does not link to the parameter.

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 clearly states the tool creates a new hero by rolling attributes and persisting a character sheet. It distinguishes itself from sibling tools like read_character_sheet and update_character_sheet which operate on existing sheets.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like update_character_sheet or archive_character, nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rc-ventura/fantasy-gamebook-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server