Skip to main content
Glama
fbwndrud

vibelore

by fbwndrud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lore_init

Idempotent

Create a blank novel project foundation for authors to fill manually, or adopt an existing world/setting.md directory without overwriting it.

Instructions

작가가 직접 채울 빈 작품 기반(world/setting.md, 빈 chapters·summaries·characters 디렉터리, .vibelore/foundation.json)을 만들거나, world/setting.md가 이미 있는 디렉터리를 쓰기 없이 이어받는다. 모델이 세계·인물을 자동 설계하게 하려면 이 도구 대신 lore_profile → lore_profile_decide → lore_create를 쓴다. lore_create는 기반이 있으면 거부하므로 둘 중 하나만 쓴다. 새 작품은 언어 계약 검증 때문에 보통 status=needs_model을 한 번 돌려주며 lore_resume으로 답해야 저장된다. 재호출은 덮어쓰지 않고 adopted=true와 현재 상태를 돌려준다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreYes엔진 장르 id(예: mystery-thriller, romantasy, regression-hunter, cozy, other). 틀리면 사용 가능 목록과 함께 거부한다. 기존 작품을 이어받을 때는 무시된다.
workIdYes작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다.
povModeNo자유 텍스트 시점(예: 3인칭제한, 1인칭). omniscient·multi-pov는 단일 화자 검사를 생략하고 none은 시점 검사를 끈다. 생략하면 제한 3인칭.
projectNo작품 디렉터리의 절대 경로. 생략하면 서버 실행 디렉터리.
languageNo작품 언어 BCP 47 태그(예: ko, en-US, ja, zh-Hant). 생략하면 저장된 계약을 따른다.
worldFactsNo변하지 않는 세계 사실 5~10개. w1..wN id로 world/setting.md에 기록된다.
targetChaptersNo완결 목표 화수. 아크 위치 계산에 쓰인다. 생략하면 저장하지 않는다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.4
    • changedInput schema / properties / genre / description
      Previous value: -"엔진이 아는 장르 id. 틀리면 목록을 알려준다."New value: +"엔진 장르 id(예: mystery-thriller, romantasy, regression-hunter, cozy, other). 틀리면 사용 가능 목록과 함께 거부한다. 기존 작품을 이어받을 때는 무시된다."
    • changedInput schema / properties / povMode / description
      Previous value: -"예: 3인칭제한, 1인칭"New value: +"자유 텍스트 시점(예: 3인칭제한, 1인칭). omniscient·multi-pov는 단일 화자 검사를 생략하고 none은 시점 검사를 끈다. 생략하면 제한 3인칭."
    • changedInput schema / properties / targetChapters / description
      Previous value: -"완결 목표 화수. 아크 위치 계산에 쓰인다."New value: +"완결 목표 화수. 아크 위치 계산에 쓰인다. 생략하면 저장하지 않는다."
    • changedInput schema / properties / workId / description
      Previous value: -"작품 식별자 ([A-Za-z0-9_-])."New value: +"작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다."
    • changedInput schema / properties / worldFacts / description
      Previous value: -"변하지 않는 세계 사실 5~10개."New value: +"변하지 않는 세계 사실 5~10개. w1..wN id로 world/setting.md에 기록된다."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safe-write profile is covered. The description adds genuine context beyond that: re-calling does not overwrite but returns adopted=true plus current state, and new works typically return status=needs_model requiring lore_resume before saving. That is useful but not rich enough to max out against annotations that already carry the safety semantics.

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?

Front-loads the core create/adopt purpose before alternatives and workflow caveats, and every sentence carries information. It is slightly dense across multiple clauses, but there is no filler.

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

Completeness5/5

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

For a 7-parameter, no-output-schema tool, the description covers purpose, adoption semantics, sibling exclusivity, and the multi-step needs_model/lore_resume saving flow. An agent has everything needed to call it correctly and handle the response.

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 description coverage is 100%, so the schema already documents genre examples and rejection behavior, povMode omniscient/multi-pov handling, language fallback, and project defaulting. The description adds no parameter-level detail beyond what the schema supplies, so baseline 3 is correct.

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?

States a specific verb and resource with concrete artifacts (world/setting.md, empty chapters/summaries/characters dirs, .vibelore/foundation.json) and adds the adoption branch explicitly. It also names the sibling it is not (the lore_profile → lore_profile_decide → lore_create chain), so an agent can distinguish it without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use the profile/decide/create chain for model-driven design, use this tool for an author-filled blank foundation, and notes lore_create rejects when a foundation exists so only one is used. Adds the needs_model → lore_resume follow-up flow, which no other field provides.

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

Deploy Server

Other Tools