Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Set writing style guide

set_writing_style_guide

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": {
      "channel": "<channel>",
      "guide": "<guide>"
    },
    "name": "set_writing_style_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
guideYesThe whole new guide; an empty string clears it.
channelYesThe channel whose guide to replace.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnlyHint=false annotation, the description discloses that a set guide overrides the communication style stored in memory and that other channels keep their guides, which is meaningful precedence and scope information. It also warns that user-authored or user-approved text is replaced and instructs the agent to report changes. It does not say whether prior guides are recoverable or versioned, which is the main residual gap given destructiveHint=false on an overwriting operation.

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 with the core action, then usage, then the edit procedure, and the returns block is clearly separated. Slightly repetitive around replacement ("It replaces text the user wrote or approved" followed by "keep everything they didn't ask to change"), but no sentence is wasted.

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 three-parameter mutation tool with no output schema, the description covers action, scope isolation, precedence over memory, the required read-modify-write flow, and return contents via the embedded returns block. An agent has enough to call it correctly without further discovery.

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 the baseline is 3, but the description adds real meaning: the guide parameter must be the whole new guide, assembled by reading with get_writing_style_guide and stripping the notes that tool appends. That is a non-obvious input contract the schema does not express.

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 and resource: "Replace the user's writing style guide for one channel, the voice Sliq writes in there." It also names the sibling it pairs with (get_writing_style_guide), so an agent can distinguish a full replacement from a read 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?

Gives explicit when-to-use guidance ("when the user wants to sound different in a channel that has a guide, change the guide") and names the alternative plus the exact read-modify-write procedure via get_writing_style_guide. It also states a preservation rule for text the user didn't ask to change.

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

All Sliq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources