Skip to main content
Glama

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+]
  3. 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"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already mark readOnlyHint=true, so the description doesn't need to re-establish safety; it adds the useful context that the returned guide should be followed. It does not disclose output format or any further behavioral constraints, but none are required for this simple getter.

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?

The description is one efficient sentence with a front-loaded action, followed by the usage instruction and a parameter pointer. No redundant words.

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 one-parameter, read-only tool with no output schema, the description covers what it returns and when to use it. It could explicitly state the return format (e.g., text/markdown), but 'guide' is sufficient for an agent to know what to expect.

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

Parameters2/5

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

Schema description coverage is 0% and the only parameter guidance is '`skill` selects the guide,' which mostly restates the parameter name. The description does not compensate for the enum's lack of descriptions, so an agent must infer the meaning of each skill value from the enum labels themselves.

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 clearly states the verb ('Return') and resource ('best-practice guide for a Sliq workflow'), and the added 'read and follow it before acting' frames the tool's role. This distinguishes it from sibling getters like get_personalization_guide and get_writing_style_guide by scoping it to Sliq workflows generally.

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 temporal usage cue: read and follow the guide before acting on the workflow. It does not name alternatives or exclusion cases, but the context is clear enough for a single-purpose getter.

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