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.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true. The description reinforces the read-only nature and adds useful context: research is already saved, calling avoids re-spending credits, and results may be truncated. It matches the annotation and provides behavioral clarity beyond the schema.

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 structured with a summary tag and a returns tag. Every sentence earns its place: purpose, when-to-use, and return shape are all present without fluff or repetition.

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?

Even though there is no output schema, the description explicitly documents the returned dict shape and fields. Combined with full parameter schema coverage and readOnlyHint, an agent has enough context to select, invoke, and interpret the result 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%, so the schema fully documents agent_id, person, limit, and offset. The description adds no parameter-specific details beyond what the schema already states, which is fine given the baseline for full schema coverage.

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?

Description states a specific verb+resource: 'Read back personalization research already saved for an agent.' It clearly distinguishes from write/research tools like save_prospect_research or query_prospects by emphasizing it retrieves already-saved findings.

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: 'Call 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?' It does not name alternatives or exclusion conditions, so a half-point is held back.

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