Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Query suggested deals

query_suggested_deals
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": "query_suggested_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax people (default 50, capped at 200).
offsetNoPeople to skip for paging; re-call with offset += limit while has_more is true.
removedNoList the people removed from the suggestions instead.
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. Added

TDQS

A4.8/5.0
Behavior5/5

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

With only readOnlyHint=true supplied, the description carries real weight: it discloses ordering (strongest stage first, then most recent), the qualifying condition (reply reached interested or meeting_booked), the empty-result cause (deal rule off), and removal semantics (newest first, team-wide effect of one teammate's removal). It also documents the return payload since no output schema exists.

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-loaded with the core definition and use case, then paging/returns detail in a separate block. The core sentence is dense and slightly run-on ('people with no deal whose reply to the user's outreach, or to a teammate's, reached a stage...'), costing some readability, but no sentence is filler.

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?

For a read-only query with no output schema, the description covers everything needed: eligibility rule, ordering, empty-result condition, alternate removed mode, the create_deal handoff, and a full return-shape description including field meanings. Nothing an agent needs to call it correctly is missing.

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 limit/offset/on_behalf_of need no elaboration. The description nonetheless adds meaning beyond the schema for removed=true (ordering of removals and team-wide scope) and defines the semantics of the returned id, outcome, at, and contacted_by fields, which the schema cannot express.

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 (list) and a precisely defined resource: people with no deal whose reply reached a stage the team's deal rule watches. It ties the concept to the product surface ('the Deals view's Suggested deals') and is clearly distinct from siblings like query_deals, query_people, and create_deal.

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?

Gives explicit trigger phrases ('who should I open a deal for?', 'any suggested deals?') and names the next tool to call (create_deal with the person's id as person_id). It also states a when-not condition: while the team's deal rule is off, nothing is suggested, and it explains the removed=true alternative mode.

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