Skip to main content
Glama
fbwndrud

vibelore

by fbwndrud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lore_writer_decide

Idempotent

Approves or rejects a selected WriterSkill. Approval proceeds to arc planning; rejection requires regeneration with feedback.

Instructions

lore_writer_skill이 오디션으로 고른 WriterSkill을 승인(active)하거나 거절(rejected)한다. 다른 후보로 바꾸는 기능은 없으므로 원하지 않으면 거절 후 feedback과 함께 다시 생성한다. 모델 호출 없음. WriterSkill이 없으면 오류. 반환은 {approved, skill}. 승인 뒤 다음 단계는 lore_arc_plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesapprove=active로 전환한다(생성 때 받은 검증 영수증이 없거나 이후 정본이 바뀌었으면 status=clean_fail). reject=rejected로 표시하고 파일은 지우지 않는다. 거절 뒤에는 lore_writer_skill을 feedback과 함께 다시 호출한다.
workIdYes작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다.
projectNo작품 디렉터리의 절대 경로. 생략하면 서버 실행 디렉터리.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.4
    • addedInput schema / properties / action / description
      Added value: +"approve=active로 전환한다(생성 때 받은 검증 영수증이 없거나 이후 정본이 바뀌었으면 status=clean_fail). reject=rejected로 표시하고 파일은 지우지 않는다. 거절 뒤에는 lore_writer_skill을 feedback과 함께 다시 호출한다."
    • changedInput schema / properties / workId / description
      Previous value: -"작품 식별자 ([A-Za-z0-9_-])."New value: +"작품 식별자 ([A-Za-z0-9_-]). 한 디렉터리에는 작품 하나만 둔다."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent. The description adds genuine context beyond them: no model invocation occurs, a missing WriterSkill raises an error, and the response is {approved, skill}. It does not cover the clean_fail side-effect path, so it stops short of a 5.

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

Conciseness5/5

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

Front-loads the core action, then adds only high-value clauses (no swap, no model calls, error condition, return shape, next step). No redundancy and nothing 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 mutation decision tool with annotations and no output schema, the description covers error behavior, return shape, and workflow positioning. An agent has everything needed to call it correctly and route to the next step.

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 coverage is 100% and the action enum's approve/reject semantics are fully described in the schema itself. The description names the action concept but adds no format or value detail beyond the schema, so the baseline 3 applies.

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 pair (approve/reject) and the exact resource: the WriterSkill chosen by lore_writer_skill's audition. It names the sibling that produces the target and distinguishes the boundary ('no swap function'), so an agent can separate this from lore_writer_skill without opening either schema.

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?

Explicit about the disallowed path (no swapping candidates), the correct workaround (reject, then regenerate via lore_writer_skill with feedback), and the follow-on step after approval (lore_arc_plan). When-to-use and what-not-to-do are both stated.

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