OrgLines

Find stale leads

stale_leads

Read-only

List the caller's stale CRM leads in their active workspace: leads still in status 'new' with no contact for at least N days ('days'; defaults to the workspace's auto-triage threshold, else 7; clamped 1..365), oldest-touch first. These are exactly the leads the daily auto-triage would move to 'waiting_response'. Read-only; only the caller's own workspace is scanned. Paged: 'limit' (default 20, max 100), 'cursor' (next_cursor); 'total' is the full count. 'fields' keeps only those keys; mode='summary' gives counts by source + the oldest rows.

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

Input Schema

Name	Required	Description
`days`	No
`mode`	No	'summary' = counts + the top rows only (a few KB).
`limit`	No
`cursor`	No	next_cursor from the previous page.
`fields`	No	Only these keys in each row ('id' always kept).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only and closed-world, and the description adds substantive context beyond them: the workspace-scoped scan boundary, the default-derivation rule for 'days' (workspace auto-triage threshold, else 7) with a clamp of 1..365, and paging semantics including that 'total' is the full count. These are behaviors an agent cannot read off the annotations or schema.

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 purpose and the stale definition, then behavior, then parameters — a logical order with no filler sentences. The dense parenthetical nesting (defaults, clamps, modes in one paragraph) costs a little readability, so not a 5.

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?

Five optional parameters, no output schema, and a read-only profile are all accounted for: paging, total count, field projection, summary mode, and the workspace scan scope are each addressed. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 60% schema coverage, the description carries the gaps well: it supplies the default and clamp for 'days' (absent from the schema), the default 20 and max 100 for 'limit', how 'cursor'/'next_cursor' chain, that 'fields' filters keys, and that 'mode=summary' returns counts by source plus the oldest rows. This meaningfully exceeds what the schema states.

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 and resource ('List the caller's stale CRM leads') plus the exact predicate that makes a lead stale ('status new with no contact for at least N days') and the sort order ('oldest-touch first'). That predicate cleanly separates it from generic lead-listing siblings like list_leads or search_leads without needing to name them.

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 a concrete selection criterion in prose: this returns 'exactly the leads the daily auto-triage would move to waiting_response', which tells an agent when this is the right tool. It stops short of naming an alternative tool and a when-not condition, so it does not reach a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OrgLines tools Inspect

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

Need Help?