Skip to main content
Glama
rc-ventura

Fantasy Gamebook Engine

by rc-ventura

flee_combat

Escape from combat when allowed, spending 2 stamina to avoid fighting.

Instructions

Flee the combat (if allowed); costs 2 stamina.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
combat_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endedNo
hero_aliveNo
damage_takenNo
hero_staminaYes
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only states the stamina cost, omitting other behavioral aspects like success conditions, failure consequences, or state changes.

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 description is very concise with one sentence that earns its place, but it is overly terse and could include more detail without sacrificing clarity.

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

Completeness1/5

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

Given the context of a combat system with multiple related tools and an output schema, the description is severely incomplete, lacking prerequisites, success criteria, and output explanation.

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 schema shows 'combat_id' with no description, and the tool description adds no information about what this parameter represents or how to obtain it.

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?

The description clearly states 'Flee the combat' with a specific verb and resource, distinguishing it from sibling tools like 'end_combat' or 'resolve_combat_round'.

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?

The description mentions 'if allowed' but provides no criteria for when fleeing is allowed, nor compares to alternatives like 'end_combat' or 'resolve_combat_round'.

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