Skip to main content
Glama
fbwndrud

vibelore

by fbwndrud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lore_configure

Idempotent

Configure review, tracking, and draft-section settings for a novel project, or read its NarrativeContract status and missing stages before the next commit.

Instructions

작품 설정을 조회하거나 바꾼다. 인자 없이 호출하면 읽기 전용으로 StoryProfile·StorySpine·WriterSkill을 하나의 NarrativeContract로 묶어 status(ready|incomplete), 누락 단계(missing), 언어·분량 계약, 검토·추적 설정을 돌려준다. disabledReviews·disabledDraftSections·tracking·customTracking·mergeRecords 중 하나라도 넘기면 .vibelore/review-policy.json에 저장한다. 목록과 tracking 객체는 통째로 교체되고(빈 배열=모두 켬), mergeRecords만 누적된다. 변경은 다음 커밋부터 적용되며 이미 쓴 화는 바뀌지 않는다. 모델 호출 없음.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workIdYes작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다.
projectNo작품 디렉터리의 절대 경로. 생략하면 서버 실행 디렉터리.
trackingNo추적 기능 켜기/끄기. 기본은 모두 켜짐. objects=물건·장소·단서·능력, knowledge=누가 무엇을 아는가, scheduled=일어나기로 된 일(회귀 전생 사건·예언·예약), hooks=떡밥.
mergeRecordsNo같은 대상으로 확인된 기록 병합(from을 into에 흡수). 후보는 조회 결과의 mergeCandidates에 있다. 기존 병합에 누적되며 다음 커밋부터 반영.
customTrackingNo작가 정의 추적 항목 전체 목록(교체). pinned=매 화 입력에 항상 포함. rules: monotonic{field,direction:up|down,unless?}, frozenAfter{status}, speakerOnly{alias,by}; severity soft(기본)|hard. note=검토 모델에 보여줄 자연어 규칙(advisory).
disabledReviewsNo끌 검토 목록 전체(빈 배열이면 모두 켬). 꺼진 검토는 요청하지 않고 실패로 보지 않는다. 연속성 추출·검사는 끌 수 없다.
disabledDraftSectionsNo초고 요청에서 뺄 선택 섹션 목록 전체(빈 배열이면 모두 넣음): older-memory=오래된 관련 기억, previous-tail=직전 화 말미, author-craft=작법 묶음, style-anchor=문체 기준 예시. 계획·설정·현재 상태·최근 요약은 뺄 수 없다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.4.4
    • addedInput schema / properties / customTracking / items / properties / feature / description
      Added value: +"어느 추적 기능에 붙일지."
    • addedInput schema / properties / customTracking / items / properties / name / description
      Added value: +"항목 이름. 같은 이름은 같은 id를 유지한다."
    • changedInput schema / properties / mergeRecords / description
      Previous value: -"같은 대상으로 확인된 기록 병합(from을 into에 흡수). 다음 커밋부터 반영."New value: +"같은 대상으로 확인된 기록 병합(from을 into에 흡수). 후보는 조회 결과의 mergeCandidates에 있다. 기존 병합에 누적되며 다음 커밋부터 반영."
    • addedInput schema / properties / mergeRecords / items / properties / from / description
      Added value: +"흡수될 기록 id"
    • addedInput schema / properties / mergeRecords / items / properties / into / description
      Added value: +"남길 기록 id"
    • changedInput schema / properties / workId / description
      Previous value: -"작품 식별자 ([A-Za-z0-9_-])."New value: +"작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the write target path, that lists and tracking objects are replaced wholesale (empty array = all on) while mergeRecords alone accumulates, that changes apply only from the next commit and never rewrite already-written episodes, and that no model calls occur. These are exactly the mutation semantics an agent needs.

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?

Dense but well ordered: read behavior first, then write trigger, then replacement/accumulation rules, then commit-scope caveat and no-model-call note. Every sentence carries information; only minor redundancy in restating defaults.

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 dual-mode mutation tool with no output schema and no annotation detail, the description covers return shape (status ready|incomplete, missing, language/length contract), file target, persistence semantics, and temporal scope. An agent has everything needed to call it correctly.

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 coverage is 100%, so parameters are already documented, yet the description adds real semantics: default all-on for tracking, replace-vs-accumulate behavior per parameter group, and the merge-from-query-result (mergeCandidates) workflow. This meaningfully exceeds the schema baseline of 3.

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?

States a specific verb+resource (작품 설정 조회/변경) and clearly explains the dual read/write nature: no-argument calls bundle StoryProfile·StorySpine·WriterSkill into a NarrativeContract. It does not differentiate itself from the sibling lore_status, which plausibly covers similar status territory, so it falls short of a 5.

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

Usage Guidelines4/5

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

Explicitly splits behavior by invocation: no arguments = read-only contract, any of the five config keys = write to .vibelore/review-policy.json. That is clear when-to-use guidance, but no alternative sibling is named for the read path and no when-not-to-use exclusion is given.

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