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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
-}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate this is not read-only and not destructive. The description adds meaningful behavioral context: Sliq automatically stamps the user, surface, and agent, and the summary is read by a teammate with no other context. This helps the agent understand downstream consequences and how to write the summary.

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 tightly written and front-loaded with the core purpose. Every sentence contributes: the trigger condition, the guidance to escalate rather than change topic, the auto-stamping behavior, and summary content instructions. The returns section is brief and useful.

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 simple two-parameter tool, the description fully covers when to use it, what to write, what happens after, and what the return value looks like. Even without an output schema, the returns note gives the agent enough to know what to expect.

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. The description adds value by specifying what the summary should contain ('what the user wanted, what went wrong, and what you already tried'), which goes beyond the schema's 'plain-text description' and improves the agent's ability to fill the parameter correctly.

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 states a specific action ('Flag a problem to the Sliq team') and a clear trigger condition ('when you're stuck and a human should step in — something you can't resolve'). It clearly distinguishes this from ordinary problem-solving by requiring that the agent has already tried its own tools.

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?

Provides explicit when-to-use guidance: after trying and failing to resolve with own tools. It also says to prefer this over switching subject or channel. It doesn't name specific sibling alternatives, but the boundary between escalation and normal resolution is clear.

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