Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Escalate To Team

escalate_to_team

Sliq stamps the affected user, the surface, and the agent automatically, so write the summary for a teammate with no other context: what the user wanted, what went wrong, and what you already tried. Dict confirming the flag was raised, with a note on what to tell the user next.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesPlain-text description of the problem and what you already tried.
agent_idNoThe agent this concerns. Defaults to the current agent when in one; pass it only to point at a different agent.
on_behalf_ofNoAn 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The agent this concerns. Defaults to the current agent when in one;\npass it only to point at a different agent."
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "The task this concerns. Defaults to the current task when in one;\npass it only to point at a different task."
-}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations mark it as non-read/non-destructive but only weakly characterize the write. The description adds real value: Sliq auto-stamps user/surface/agent, a human reads and follows up, and it is a one-way async handoff. It does not cover rate limits or auth requirements, but the post-call behavior is well disclosed.

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-loads the core purpose and the precondition, with every sentence contributing. The XML-ish summary/returns structure is slightly heavier than needed but not padded.

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 3-parameter, no-output-schema tool this is complete: it covers when to use it, what to put in the summary, what the system fills in automatically, and what the return contains (a note on what to tell the user). Nothing an agent needs to call it correctly 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%, so the baseline is 3, but the description adds genuine meaning: it tells the agent how to write `summary` (what the user wanted, what went wrong, what was tried) and implies agent_id is usually unnecessary because it is auto-stamped. This goes beyond the schema's terse field text.

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+resource (flag a problem to the Sliq team) and clarifies the exact situation that triggers it — something the agent cannot resolve with its own tools after trying. This distinguishes it clearly from siblings like request_user_action, report_enactment_blocked, and retry_blocked_enactment.

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?

Gives an explicit when ('when you're stuck and a human should step in... after trying') and a when-not ('rather than switching subject or channel when you've hit a wall'). It stops short of naming a specific sibling alternative, so it is clear but not fully routed.

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