Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get skill guide

get_skill_guide
Read-only

Return the best-practice guide for a Sliq workflow — read and follow it before acting on that workflow. skill selects the 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": {
      "skill": "<skill>"
    },
    "name": "get_skill_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYes
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. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
-  "blog_content_calendar",
-  "blog_post_writing",
-  "company_monitor",
-  "email_inbox_management",
-  "email_sequence_setup",
-  "exa_find_people",
-  "find_companies_news_scan",
-  "find_companies_news_scan_setup",
-  "find_companies_search_criteria",
-  "find_companies_webset_mode",
-  "find_people",
-  "find_warm_intro_paths",
-  "linkedin_flowless_campaigns",
-  "linkedin_outreach",
-  "linkedin_outreach_debugging",
-  "linkedin_outreach_finding_leads",
-  "linkedin_outreach_operations",
-  "linkedin_outreach_warmup",
-  "linkedin_post_monitoring",
-  "linkedin_post_writing",
-  "message_tagging",
-  "mixed_channel_outreach",
-  "news_scan_predictleads",
-  "news_scan_tavily",
-  "news_scan_theirstack",
-  "posthog_setup",
-  "prospecting_agent",
-  "scheduling_calendar_events",
-  "segment_tagging",
-  "trigger_code",
-  "weekly_sales_review"
-]New value: +[
+  "blog_content_calendar",
+  "blog_post_writing",
+  "company_monitor",
+  "email_inbox_management",
+  "email_sequence_setup",
+  "exa_find_people",
+  "find_companies_news_scan",
+  "find_companies_news_scan_setup",
+  "find_companies_search_criteria",
+  "find_companies_webset_mode",
+  "find_people",
+  "find_warm_intro_paths",
+  "linkedin_flowless_campaigns",
+  "linkedin_outreach",
+  "linkedin_outreach_debugging",
+  "linkedin_outreach_finding_leads",
+  "linkedin_outreach_operations",
+  "linkedin_outreach_warmup",
+  "linkedin_post_monitoring",
+  "linkedin_post_writing",
+  "message_tagging",
+  "mixed_channel_outreach",
+  "news_scan_predictleads",
+  "news_scan_tavily",
+  "news_scan_theirstack",
+  "pages",
+  "posthog_setup",
+  "prospecting_agent",
+  "scheduling_calendar_events",
+  "segment_tagging",
+  "trigger_code",
+  "weekly_sales_review"
+]
  3. Changed2 schema fields changed
    • 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."
+}
    • changedInput schema / properties / skill / enum
      Previous value: -[
-  "blog_content_calendar",
-  "blog_post_writing",
-  "company_monitor",
-  "email_inbox_management",
-  "email_sequence_setup",
-  "exa_find_people",
-  "find_companies_news_scan",
-  "find_companies_news_scan_setup",
-  "find_companies_search_criteria",
-  "find_companies_webset_mode",
-  "find_people",
-  "find_warm_intro_paths",
-  "linkedin_flowless_campaigns",
-  "linkedin_outreach",
-  "linkedin_outreach_debugging",
-  "linkedin_outreach_finding_leads",
-  "linkedin_outreach_operations",
-  "linkedin_outreach_warmup",
-  "linkedin_post_monitoring",
-  "linkedin_post_writing",
-  "message_tagging",
-  "mixed_channel_outreach",
-  "news_scan_predictleads",
-  "news_scan_tavily",
-  "news_scan_theirstack",
-  "posthog_setup",
-  "prospecting_agent",
-  "scheduling_calendar_events",
-  "segment_tagging",
-  "social_listening",
-  "trigger_code",
-  "weekly_sales_review"
-]New value: +[
+  "blog_content_calendar",
+  "blog_post_writing",
+  "company_monitor",
+  "email_inbox_management",
+  "email_sequence_setup",
+  "exa_find_people",
+  "find_companies_news_scan",
+  "find_companies_news_scan_setup",
+  "find_companies_search_criteria",
+  "find_companies_webset_mode",
+  "find_people",
+  "find_warm_intro_paths",
+  "linkedin_flowless_campaigns",
+  "linkedin_outreach",
+  "linkedin_outreach_debugging",
+  "linkedin_outreach_finding_leads",
+  "linkedin_outreach_operations",
+  "linkedin_outreach_warmup",
+  "linkedin_post_monitoring",
+  "linkedin_post_writing",
+  "message_tagging",
+  "mixed_channel_outreach",
+  "news_scan_predictleads",
+  "news_scan_tavily",
+  "news_scan_theirstack",
+  "posthog_setup",
+  "prospecting_agent",
+  "scheduling_calendar_events",
+  "segment_tagging",
+  "trigger_code",
+  "weekly_sales_review"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
-  "blog_content_calendar",
-  "blog_post_writing",
-  "company_monitor",
-  "creating_todos",
-  "email_inbox_management",
-  "email_sequence_setup",
-  "exa_find_people",
-  "find_companies_news_scan",
-  "find_companies_news_scan_setup",
-  "find_companies_search_criteria",
-  "find_companies_webset_mode",
-  "find_people",
-  "find_warm_intro_paths",
-  "linkedin_flowless_campaigns",
-  "linkedin_outreach",
-  "linkedin_outreach_debugging",
-  "linkedin_outreach_finding_leads",
-  "linkedin_outreach_operations",
-  "linkedin_outreach_warmup",
-  "linkedin_post_monitoring",
-  "linkedin_post_writing",
-  "message_tagging",
-  "mixed_channel_outreach",
-  "news_scan_predictleads",
-  "news_scan_tavily",
-  "news_scan_theirstack",
-  "posthog_setup",
-  "prospecting_agent",
-  "scheduling_calendar_events",
-  "segment_tagging",
-  "social_listening",
-  "trigger_code",
-  "weekly_sales_review"
-]New value: +[
+  "blog_content_calendar",
+  "blog_post_writing",
+  "company_monitor",
+  "email_inbox_management",
+  "email_sequence_setup",
+  "exa_find_people",
+  "find_companies_news_scan",
+  "find_companies_news_scan_setup",
+  "find_companies_search_criteria",
+  "find_companies_webset_mode",
+  "find_people",
+  "find_warm_intro_paths",
+  "linkedin_flowless_campaigns",
+  "linkedin_outreach",
+  "linkedin_outreach_debugging",
+  "linkedin_outreach_finding_leads",
+  "linkedin_outreach_operations",
+  "linkedin_outreach_warmup",
+  "linkedin_post_monitoring",
+  "linkedin_post_writing",
+  "message_tagging",
+  "mixed_channel_outreach",
+  "news_scan_predictleads",
+  "news_scan_tavily",
+  "news_scan_theirstack",
+  "posthog_setup",
+  "prospecting_agent",
+  "scheduling_calendar_events",
+  "segment_tagging",
+  "social_listening",
+  "trigger_code",
+  "weekly_sales_review"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
-  "blog_content_calendar",
-  "blog_post_writing",
-  "company_monitor",
-  "creating_todos",
-  "email_inbox_management",
-  "email_sequence_setup",
-  "exa_find_people",
-  "find_companies_news_scan",
-  "find_companies_news_scan_setup",
-  "find_companies_search_criteria",
-  "find_companies_webset_mode",
-  "find_people",
-  "find_warm_intro_paths",
-  "linkedin_flowless_campaigns",
-  "linkedin_outreach",
-  "linkedin_outreach_debugging",
-  "linkedin_outreach_finding_leads",
-  "linkedin_outreach_operations",
-  "linkedin_outreach_warmup",
-  "linkedin_post_monitoring",
-  "linkedin_post_writing",
-  "message_tagging",
-  "mixed_channel_outreach",
-  "news_scan_predictleads",
-  "news_scan_tavily",
-  "news_scan_theirstack",
-  "posthog_setup",
-  "prospecting_agent",
-  "scheduling_calendar_events",
-  "social_listening",
-  "trigger_code",
-  "weekly_sales_review"
-]New value: +[
+  "blog_content_calendar",
+  "blog_post_writing",
+  "company_monitor",
+  "creating_todos",
+  "email_inbox_management",
+  "email_sequence_setup",
+  "exa_find_people",
+  "find_companies_news_scan",
+  "find_companies_news_scan_setup",
+  "find_companies_search_criteria",
+  "find_companies_webset_mode",
+  "find_people",
+  "find_warm_intro_paths",
+  "linkedin_flowless_campaigns",
+  "linkedin_outreach",
+  "linkedin_outreach_debugging",
+  "linkedin_outreach_finding_leads",
+  "linkedin_outreach_operations",
+  "linkedin_outreach_warmup",
+  "linkedin_post_monitoring",
+  "linkedin_post_writing",
+  "message_tagging",
+  "mixed_channel_outreach",
+  "news_scan_predictleads",
+  "news_scan_tavily",
+  "news_scan_theirstack",
+  "posthog_setup",
+  "prospecting_agent",
+  "scheduling_calendar_events",
+  "segment_tagging",
+  "social_listening",
+  "trigger_code",
+  "weekly_sales_review"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / skill / enum
      Previous value: -[
-  "blog_content_calendar",
-  "blog_post_writing",
-  "company_monitor",
-  "creating_todos",
-  "email_inbox_management",
-  "email_sequence_setup",
-  "exa_find_people",
-  "find_companies_news_scan",
-  "find_companies_news_scan_setup",
-  "find_companies_search_criteria",
-  "find_companies_webset_mode",
-  "find_people",
-  "find_warm_intro_paths",
-  "linkedin_flowless_campaigns",
-  "linkedin_outreach",
-  "linkedin_outreach_debugging",
-  "linkedin_outreach_finding_leads",
-  "linkedin_outreach_operations",
-  "linkedin_outreach_warmup",
-  "linkedin_post_monitoring",
-  "linkedin_post_writing",
-  "mixed_channel_outreach",
-  "news_scan_predictleads",
-  "news_scan_tavily",
-  "news_scan_theirstack",
-  "posthog_setup",
-  "prospecting_agent",
-  "scheduling_calendar_events",
-  "social_listening",
-  "trigger_code",
-  "weekly_sales_review"
-]New value: +[
+  "blog_content_calendar",
+  "blog_post_writing",
+  "company_monitor",
+  "creating_todos",
+  "email_inbox_management",
+  "email_sequence_setup",
+  "exa_find_people",
+  "find_companies_news_scan",
+  "find_companies_news_scan_setup",
+  "find_companies_search_criteria",
+  "find_companies_webset_mode",
+  "find_people",
+  "find_warm_intro_paths",
+  "linkedin_flowless_campaigns",
+  "linkedin_outreach",
+  "linkedin_outreach_debugging",
+  "linkedin_outreach_finding_leads",
+  "linkedin_outreach_operations",
+  "linkedin_outreach_warmup",
+  "linkedin_post_monitoring",
+  "linkedin_post_writing",
+  "message_tagging",
+  "mixed_channel_outreach",
+  "news_scan_predictleads",
+  "news_scan_tavily",
+  "news_scan_theirstack",
+  "posthog_setup",
+  "prospecting_agent",
+  "scheduling_calendar_events",
+  "social_listening",
+  "trigger_code",
+  "weekly_sales_review"
+]
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the meaningful convention that the returned guide is meant to be followed and should be fetched prior to acting, but it says nothing about the response's size, structure, or whether guides are static or per-account.

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?

Two short sentences, front-loaded with the purpose and then the prerequisite ordering instruction. No padding, though the trailing '`skill` selects the guide' is close to restating the parameter name and could carry more information.

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

Completeness3/5

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

With only two parameters, no output schema, and a read-only annotation, the definition covers the essentials for invocation. It leaves the agent guessing about the guide's content length and whether a single skill value may cover multiple related workflows, which matters given the large enum.

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 coverage is 50%: `on_behalf_of` is fully documented in the schema, while `skill` is an undescribed 32-value enum. The description only says '`skill` selects the guide,' which adds little beyond the enum itself and does not explain how skill names map to workflows or what to do if the relevant workflow is absent from the list.

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 states a specific verb and resource — 'Return the best-practice guide for a Sliq workflow' — and clarifies that the `skill` parameter selects which guide. It is clear what the tool does, though it does not explicitly distinguish itself from guide-adjacent siblings such as get_personalization_guide or get_writing_style_guide.

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?

It gives an explicit ordering rule: read and follow the guide 'before acting on that workflow,' which tells the agent when this call must precede other workflow actions. It stops short of naming alternatives or stating when a guide lookup can be skipped.

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