Skip to main content
Glama

transfer_item

Transfer an item to a new character holder in a specified chapter of your book project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_nameYes
new_holderYes
chapterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • FastMCP tool registration and async handler for transfer_item. Decorated with @mcp.tool(), it accepts item_name, new_holder, and chapter, then delegates to workflow.transfer_item().
    @mcp.tool()
    async def transfer_item(item_name: str, new_holder: str, chapter: int) -> str:
        try:
            return workflow.transfer_item(item_name, new_holder, chapter)
        except ValueError as e:
            return str(e)
  • Workflow-level orchestration for transfer_item. Loads the project and continuity, calls cont.transfer_item(), saves state, and returns a summary string.
    def transfer_item(item_name: str, new_holder: str, chapter: int) -> str:
        _, cont = require_project()
        cont.transfer_item(item_name, new_holder, chapter)
        save_project_and_continuity()
        return f"{item_name} → {new_holder}"
  • Core domain logic: ContinuityLog.transfer_item() finds the item by name in the inventory list and updates its current_holder and transferred_chapter.
    def transfer_item(self, item_name: str, new_holder: str, chapter: int) -> None:
        item = self.get_item(item_name)
        if item:
            item.current_holder = new_holder
            item.transferred_chapter = chapter
  • InventoryItem dataclass schema used by transfer_item. Fields: name, description, acquired_chapter, transferred_chapter, current_holder, original_holder.
    @dataclass
    class InventoryItem:
        name: str
        description: str = ""
        acquired_chapter: int | None = None
        transferred_chapter: int | None = None
        current_holder: str | None = None
        original_holder: str | None = None
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/BurgersJackson/storywright-mcp'

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