Sliq

Get writing style guide

get_writing_style_guide

Read-only

Return the user's writing style guide for one channel, to follow when drafting that channel's outreach. Pass channel='linkedin_dm' for a DM or connection note, or channel='email' for an email. A set guide is the user's own voice and overrides the default craft rules; returns a note when none is set.

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>"
    },
    "name": "get_writing_style_guide"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes	A channel a user can set a writing style guide for.
`on_behalf_of`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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."

Changed2 schema fields changedOct 20, 2026
- addedInput schema / properties / channel / description
```
Added value: +"A channel a user can set a writing style guide for."
```
- addedInput schema / properties / channel / title
```
Added value: +"WritingStyleChannel"
```

Changed2 schema fields changedOct 19, 2026

changedInput schema / properties / channel / enum

Previous value: -[
-  "linkedin_dm",
-  "email",
-  "linkedin_comment",
-  "reddit_comment"
-]New value: +[
+  "linkedin_dm",
+  "email",
+  "linkedin_comment"
+]

addedInput schema / properties / on_behalf_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "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."
+}

First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

readOnlyHint=true is consistent with a retrieval tool. Beyond the annotation, it discloses that a user-set guide overrides the default craft rules and that a note is returned when nothing is set, which meaningfully informs interpretation of the response.

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?

Three compact sentences; the core action is front-loaded, followed by channel guidance and then the precedence and empty-state behavior. Nothing is repeated or wasted.

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?

There is no output schema, and the description covers the key edge case (no guide set) plus precedence semantics for a simple two-parameter read tool. It could have said more about the shape of the returned guide text, but nothing needed for correct invocation is missing.

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%, which alone establishes a baseline of 3. The description adds real meaning by explaining two enum values (linkedin_dm = DM or connection note, email = email), though it omits the third value linkedin_comment and says nothing about on_behalf_of 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?

The description uses a specific verb and resource ("Return the user's writing style guide for one channel") and frames it around drafting outreach, which tells an agent exactly what it retrieves. It does not name a sibling or contrast with alternatives such as set_writing_style_guide or get_personalization_guide, so it falls short of full differentiation.

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?

"To follow when drafting that channel's outreach" gives a clear usage context, and the note about a set guide overriding default craft rules clarifies the precedence. It lacks an explicit when-not or a pointer to the sibling that sets the guide.

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

All Sliq tools Inspect

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

Need Help?