Skip to main content
Glama
Sign In

Layerz

by cc.layerz.app
OverviewDiscussionsAdmin

Set custom instructions

layerz_set_custom_instructions
DestructiveIdempotent

Replaces the conventions of a workspace (the personal one by default, or workspace_id): the standing instructions for AI agents its members share (plain Markdown/text, ≤ 3000 chars; an empty string clears them). They apply across every model of the workspace, on top of each model's FINANCE.md, and come back as conventions in the results of the tools that open a model of the workspace. Any member may write them. No version is persisted. Not advertised to model-scoped or read-only keys.

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": {
      "content": "<content>"
    },
    "name": "layerz_set_custom_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesWorkspace conventions, max 3000 chars. Empty string clears them.
workspace_idNoA workspace the caller belongs to (`layerz_list_models` lists them); default: personal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"Account-wide custom instructions, max 3000 chars. Empty string clears them."New value: +"Workspace conventions, max 3000 chars. Empty string clears them."
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "description": "A workspace the caller belongs to (`layerz_list_models` lists them); default: personal.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"Account-wide custom instructions (plain Markdown/text). Max 3000 chars. Empty string clears them."New value: +"Account-wide custom instructions, max 3000 chars. Empty string clears them."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the operation fully replaces (not merges) existing conventions, that an empty string clears them, that content is capped at 3000 chars, that no version is persisted, and that access is restricted for model-scoped/read-only keys. These details align with destructiveHint=true and idempotentHint=true and meaningfully expand on them.

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?

The core action and scope are front-loaded in the first clause, and the follow-on fragments each carry distinct information (applicability across models, return location, permissions, no versioning, key restrictions). It is dense and parenthetical-heavy but nearly every clause earns its place.

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 two-parameter mutation tool with no output schema, the description covers scope, default target, clearing behavior, size limit, permission model, and where the value surfaces in other tools' results. Nothing an agent needs to invoke it correctly or predict its effect is missing.

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 both `content` (max 3000, empty clears) and `workspace_id` (default personal) are already documented. The description restates the default-workspace behavior and the empty-string clear semantics but adds no new syntax or format guidance, making the baseline 3 appropriate.

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?

The description gives a specific verb ('Replaces') and resource ('the conventions of a workspace'), defines the scope (personal by default or `workspace_id`), and implicitly separates itself from read-side `layerz_get_conventions` and from `layerz_set_finance_md` by noting conventions apply 'on top of each model's FINANCE.md'. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: 'Any member may write them' and 'Not advertised to model-scoped or read-only keys' tell the agent who can call it and where it is unavailable, and 'an empty string clears them' covers the reset case. However, there is no explicit when-to-use/when-not routing against `layerz_set_finance_md` or `layerz_get_conventions', leaving alternatives to inference.

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

All Layerz toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources