Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_positioningA

いまの決め(看板)を読む。媒体を省くと全体に適用される決めを返す。

assemble_materialC

媒体向けの文面を書くための材料を取り出す。公開不可の節は落として警告に書く。

record_positioningA

売り方の決めを 1 ブロック登記する。必須の欄が欠けていれば書かずに拒否する。

日付は 2026-09-16 の形で渡す。登記が通ると、その場でパッケージ定義の鮮度と、 旧い束を宣言する提示物の件数(ファイル名つき)が返る。

register_capabilityB

機能の台帳に 1 行足す。必須欄・分類・裏づけの節が通らなければ書かずに拒否し、次の一手を返す。

revise_packageB

パッケージ定義を改訂する。台帳に無い機能名を束ねようとすれば書かずに拒否する。

通ると、その節を書き換えて最終更新日を今日に進める。節が無ければ新しく足す。

check_consistencyA

正本を制約に当て、違反の一覧を直し先つきで返す。正本は変えない。

範囲は、省略か「全体」で正本全体、媒体の名前でその媒体、提示物のファイル名でその 1 件。 実在しない名前を渡したときは、拒否ではなく実在する範囲の一覧が返る。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
ontology型・関係・制約の定義を返す。セッションの初めに読む。

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and action: reading or recording positioning, assembling material, registering capabilities, revising packages, and checking consistency. There is no meaningful overlap, and the descriptions leave no ambiguity about which tool to select.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern: get_positioning, record_positioning, assemble_material, register_capability, revise_package, check_consistency. The verbs clearly indicate the action, and the nouns identify the target resource.

Tool Count5/5

Six tools is well within the ideal scope for a focused domain. Each tool addresses a distinct part of the workflow—reading/writing positioning, preparing material, managing capabilities, editing packages, and validating consistency—without unnecessary redundancy or bloat.

Completeness4/5

The core positioning, package revision, and consistency-checking workflows are well covered, and the register_capability tool includes guardrails with next-step guidance. However, there is no direct tool to read or update the capability ledger, and delete operations are absent, which creates minor gaps for maintenance scenarios.

Maintenance

ActivityMaintained
ResponsivenessNo issues