Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Extend Find Search

extend_find_search

Add more results to a named list on an agent.

Reuses the list's original criteria — does NOT support refinement. If the user wants to narrow the criteria, tell them to start a new list (call start_find_search with a fresh list_name).

Refuses when: no webset on file for the list, a run is already in progress, the per-list cap is already reached, or (sliq mode) the balance can't afford even one more result. When the balance covers fewer than requested, the count is clamped and the result carries a clamp_notice — surface it to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe agent hosting the list.
list_nameYesThe slug the list was created with (the `list_name` column of `query_search_results`).
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.
additional_countNoHow many more results to fetch (default 20).

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. Changed1 schema field changed
    • changedInput schema / properties / list_name / description
      Previous value: -"The slug the list was created with (visible in the Output\ntab sub-pill, or via `query_search_results`'s `list_name` column)."New value: +"The slug the list was created with (the `list_name` column\nof `query_search_results`)."
  3. Changed3 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "The agent hosting the list.",
+  "type": "integer"
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "The task hosting the list.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id",
-  "list_name"
-]New value: +[
+  "agent_id",
+  "list_name"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false / destructiveHint=false, but the description adds the failure modes, the per-list cap behavior, the balance-clamping rule, and the presence of a `clamp_notice` field the agent must surface. This is unusually rich behavioral disclosure beyond structured data.

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?

Front-loaded with the core action, then constraints and failure modes in terse bullets. Every sentence carries distinct operational information; nothing is redundant padding.

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?

With no output schema, the description compensates by disclosing the `clamp_notice` return field and the refusal outcomes. It stops short of describing the general result shape (run id, counts), so it is nearly but not fully complete for an async, credit-consuming operation.

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 description coverage is 100%, so all four parameters (including on_behalf_of and additional_count) are already documented in the schema. The description reinforces list_name semantics indirectly but adds no syntax, format, or bounds detail beyond what the schema provides; baseline 3 is appropriate.

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+scope: adds more results to a named list on an agent, reusing the list's original criteria. This clearly separates it from start_find_search (new list) and query_search_results (read results), both of which are named or implied in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use it ('does NOT support refinement') and routes to the alternative ('call start_find_search with a fresh list_name'). It also enumerates refusal conditions (no webset, run in progress, cap reached, insufficient balance), leaving nothing to inference.

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