Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Query Prospect Research

query_prospect_research
Read-only

Call this BEFORE researching a lead to avoid re-doing work (and re-spending credits), or to reference prior findings in a follow-up, or to answer "what did you find about X?". Dict with count, truncated, and items array (each row {id, agent_id, person_linkedin_slug, person_linkedin_pid, person_email, subject_kind, company_domain, display_name, content, url, source, created_at}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax findings to return (default 50, newest first).
offsetNoNumber of findings to skip, for paging past `limit`.
personNoA lead handle (linkedin_url / linkedin_provider_id / email) to get just that lead's findings; omit for all research on the agent.
agent_idYesThe agent whose saved research to read.
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. Changed4 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "The agent whose saved research to read.",
+  "type": "integer"
+}
    • changedInput schema / properties / person / description
      Previous value: -"A lead handle (linkedin_url / linkedin_provider_id / email) to\nget just that lead's findings; omit for all research on the task."New value: +"A lead handle (linkedin_url / linkedin_provider_id / email) to\nget just that lead's findings; omit for all research on the agent."
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "The task whose saved research to read.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id"
-]New value: +[
+  "agent_id"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by disclosing the credit-spend motivation and the exact return envelope (count, truncated, items with field list), which matters because there is no output schema. No auth or cross-account behavior is discussed in the description, but the schema's on_behalf_of field carries that.

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 one-line summary, then tucks usage triggers and the return shape into tagged blocks that are easy to scan. The enumerated returns field list is verbose but earns its place because no output schema exists.

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?

For a 5-parameter read tool with no output schema, the description supplies the reader's philosophy (check before re-spending) and the full return shape, which is the main gap the missing output schema would otherwise leave. It is not exhaustive on pagination semantics or agency-account behavior, but those live in the schema.

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 limit/offset/person/agent_id/on_behalf_of are already fully documented in the schema. The description adds no parameter-level detail (no mention of the person filter or agency client scoping), so baseline 3 is correct.

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: 'Read back personalization research already saved for an agent.' The phrase 'already saved' cleanly separates it from the write-side sibling save_prospect_research, so an agent can route correctly without opening either schema.

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 three concrete invocation scenarios: before researching a lead (to avoid re-spending credits), to reference prior findings in a follow-up, and to answer 'what did you find about X?'. Strong positive guidance, though it names no explicit when-not condition or alternative tool.

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