Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Query Segment People

query_segment_people
Read-only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (default 200).
offsetNoPage offset (default 0).
tag_idNoNarrow to people carrying this tag; omit for all classified people.
channelNo'linkedin' or 'email' to read the outcome from; omit for both.
sendersNoNarrow to people reached by these teammates (emails from a group's `senders`), and read their outcome from those teammates' prospects only. Omit for every teammate; an email not in the workspace is dropped, and if none remain the result is empty.
group_idYesThe segment group to read (from list_segment_groups).
untaggedNoNarrow to the 'No match' people (classified as nothing, empty `tags`); takes precedence over `tag_id`. Omit for all classified people.
agent_idsNoScope to people with a prospect in one or more campaigns (agent_tasks ids); omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / agent_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Scope to people with a prospect in one or more campaigns (agent_tasks ids); omit\nfor all."
+}
    • addedInput schema / properties / senders
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Narrow to people reached by these teammates (emails from a group's `senders`), and\nread their outcome from those teammates' prospects only. Omit for every teammate; an\nemail not in the workspace is dropped, and if none remain the result is empty."
+}
    • removedInput schema / properties / task_ids
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "integer"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Scope to people with a prospect in one or more campaigns (agent_tasks ids); omit\nfor all."
-}
    • addedInput schema / properties / untagged
      Added value: +{
+  "default": false,
+  "description": "Narrow to the 'No match' people (classified as nothing, empty `tags`); takes\nprecedence over `tag_id`. Omit for all classified people.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses newest-classification-first ordering, OR-ed outcome semantics across outreach, empty tags for 'No match' people, and total-before-paging behavior. These details add meaningful behavioral context and do not contradict the annotation.

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 summary is front-loaded with the core purpose, then organized into filter guidance, pagination, and a dedicated returns block. Each section earns its place even with an 8-parameter tool.

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, but the returns block supplies a full field-level shape and explains the canonical person identity and outcome OR-ing. Combined with fully described schema parameters, the definition gives an agent enough to select and invoke the tool correctly.

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 extra meaning by explaining the pagination tail reachability and framing filters as user-selectable drill-downs, though many parameter meanings are already well documented in the schema.

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 opens with 'The per-person drill-down for a segment group', naming a specific operation and resource. It further distinguishes itself from segment-level tools by specifying that it returns classified people, their tags, identity, and OR-ed outcome flags.

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?

The summary gives concrete filter guidance for tag_id, untagged, agent_ids, senders, and pagination, including the total-before-paging caveat. It does not name alternative sibling tools or state when not to use this tool, so it stops short of a 5.

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