Skip to main content
Glama

Next connection to remove

connections_next

Returns the next connection to review, prioritizing spam then borderline with its level and remaining daily removals; checks safety caps and waits without removing or contacting LinkedIn.

Instructions

Returns the next connection to check, clear spam first and then borderline (never core or low), with its level and the removals left today. It first checks the halt file, the daily cap (25, 50 or 80 as the days since the last warning go by) and the sitting cap (25, or 40 from day 8; a new sitting starts after 30 minutes idle), and waits a random 15 to 45 seconds since the last removal. It removes nothing and does not contact LinkedIn.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4/5.0
Behavior4/5

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

Well beyond the annotations, it discloses the internal gating (halt file, daily cap of 25/50/80, sitting cap of 25/40 with a 30-minute idle reset) and a 15–45 second randomized wait, warning the agent that the call can block and may return nothing. It also clarifies there are no external side effects ('does not contact LinkedIn'), consistent with openWorldHint=false and destructiveHint=false. The gap is that it never says what is actually returned when the halt file or a cap blocks the call — an empty result, a null, or an explanatory object.

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?

The first sentence front-loads purpose, priority order and return payload, and the second covers the gating and timing. The second sentence is a long run-on that packs in cap numbers the agent cannot act on, but that detail does explain why an empty return can occur, so it mostly earns its place.

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 zero parameters and no output schema, the description carries the burden and does describe the return payload fields (level, removals left today) plus the blocking conditions. It stops short of stating the failure/empty-result shape or whether the call mutates local sitting state, which matters given readOnlyHint=false on a tool that 'removes nothing'.

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?

The schema declares no parameters at all, which is the baseline-4 case; there is no argument meaning for the description to add. The cap and timing numbers described are internal state, not inputs, so their absence from the schema is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns the next connection to check, in spam-then-borderline priority, together with its level and remaining removals today. That is far more precise than the title 'Next connection to remove', which it in fact corrects by saying it removes nothing. It does not name a sibling (e.g. connections_check or connections_mark) as the follow-up step, which keeps it just below the top score.

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?

Clear context for use: pull one item at a time, and the queue never yields core or low connections, which implicitly tells the agent this tool is not the way to reach those tiers. It never explicitly names an alternative tool for performing the check or mark, so the routing guidance is inferred rather than stated.

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