Skip to main content
Glama
Sign In
entry-offline-mcp

entry-offline-mcp

by l2l2l4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

entry_set_script

Set or append an object's Entry code using Python or block arrays, with variables, lists, signals, and functions generated automatically.

Instructions

오브젝트의 코드를 설정합니다. python 또는 blocks 중 하나를 주세요. python: 엔트리파이썬 코드(이벤트는 def when_start():, def when_press_key("space"): 등). 엔트리 자체 변환기로 블록으로 바뀌며, 쓰인 변수/리스트/신호/함수가 자동 생성됩니다. 'import Entry'는 생략 가능. blocks: 스레드 배열 [[이벤트블록, 블록, ...], [...]] (compact 형식, entry_guide 참고). 숫자/문자 리터럴, 드롭다운은 값 또는 이름(변수/신호/오브젝트/모양/소리/장면 이름 → id 자동 변환). mode='replace'(기본: 기존 코드 전부 교체) | 'append'(기존 코드 뒤에 스레드 추가). 결과의 warnings를 반드시 확인하세요(없는 모양/변수 등).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object": "<object>"
    },
    "name": "entry_set_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
blocksNo
objectYes오브젝트 이름 또는 id
pythonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that the default mode replaces ALL existing code, that variables/lists/signals/functions are auto-created, that names are auto-converted to ids, and that the result carries warnings to inspect. It stops short of describing failure behavior for malformed code or permission requirements.

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-loaded purpose sentence, then labeled sections per parameter, then the default and the warnings caveat. Dense but every sentence carries information; no filler or repetition.

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

Completeness4/5

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

For a mutating tool with no annotations, no output schema and low schema coverage, the description supplies format conventions, side effects, defaults, and the warnings-in-result caveat. Only error/validation behavior and any auth expectations are left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only 'object' is documented), so the description must compensate and it does — it defines the python event-function conventions, the blocks thread-array shape, the enum-like 'value or name' dropdown semantics, and the mode default. This is meaning well beyond the schema.

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?

Opens with a specific verb+resource ('오브젝트의 코드를 설정합니다') and immediately clarifies that it accepts either python or blocks, which distinguishes it from the read counterpart entry_get_script. It never names a sibling explicitly, but the verb/resource pair is unambiguous.

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?

States a real usage constraint not enforced by the schema ('python 또는 blocks 중 하나를 주세요') and explains the replace-vs-append choice with the default called out. It gives no explicit when-not-to-use or prerequisite guidance, which keeps it short of a 5.

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