Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get outreach approval

get_outreach_approval
Read-only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_outreach_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoThe agent whose effective settings to read. When omitted, reads the current agent's settings if this chat is tied to one, otherwise the account-wide settings.
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
    • 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."
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The agent whose effective settings to read. When omitted, reads the current\nagent's settings if this chat is tied to one, otherwise the account-wide settings."
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "The agent (task) whose effective settings to read. When omitted, reads the current\nagent's settings if this chat is tied to one, otherwise the account-wide settings."
-}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

readOnlyHint already covers safety, but the description goes well beyond it: it explains that an unsent `pending_approval` message is expected behavior produced by this gating, not a failure, and it spells out the override vs account-wide fallback logic. That is exactly the disambiguating context an agent needs to avoid misdiagnosing a stuck send.

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?

The summary is front-loaded with the core concept and the operational warning, and each subsequent clause adds real information rather than filler. It is somewhat verbose with the XML wrapper tags and a long returns block, but no sentence is wasted.

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?

There is no output schema, yet the description supplies a returns section documenting `settings`, `override_active`, `account_settings`, and the meaning of the true/false subtype keys. Together with the scoping guidance, an agent can both call and interpret this tool correctly.

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 100% and the schema already documents the agent_id fallback chain, so the description's recapping of that resolution adds little new. The `on_behalf_of` parameter, including its agency-client email form and credit implications, is not addressed anywhere in the description. Baseline 3 is appropriate given the schema carries the parameter burden.

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 names a specific resource and what it governs: 'the per-subtype approval settings that decide whether each kind of outbound message auto-sends or waits for the user's approval'. That is far more than a restatement of the name and lets an agent distinguish settings from the pending messages themselves. It never names the read/write sibling tools (set_outreach_approval, get_pending_approvals), so differentiation is inferential rather than explicit.

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 a concrete trigger for calling: read this before telling the user a send looks stuck, because `pending_approval` is a normal gated state. It also explains the agent_id scoping decision (specific agent override vs account-wide vs current chat agent). It stops short of naming alternative tools for related questions, so it lacks explicit when-not guidance.

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