Skip to main content
Glama

Check a profile before removal

connections_check
Read-only

Compares a LinkedIn profile page against the stored connection to decide REMOVE or SKIP, returning the level and reason. Use it to clean up connections with live proof before acting.

Instructions

Compares what a profile page shows now with the stored connection and returns REMOVE or SKIP with its level (core, spam, borderline, low, nolink) and a reason. REMOVE needs live proof: spam still shown in the headline or company, a sales-pitch headline, or a bare profile (no headline, no company, fewer than bare_mutuals mutual connections). SKIP when the name differs, the degree is not 1st, a rescue place or mission words show, or the level is core or low. Pass company and mutuals; without them a bare profile is never removed. It reads local files only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "name": "<name>",
      "degree": "<degree>",
      "location": "<location>",
      "headline": "<headline>"
    },
    "name": "connections_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe connection's LinkedIn profile URL, as in Connections.csv.
nameYesThe name shown on the profile page.
degreeYesThe connection degree shown on the page, for example "1st".
companyNoThe current company shown on the page; empty when none.
mutualsNoThe "N mutual connections" count; 0 when the page shows none.
headlineYesThe headline on the profile page; empty when none.
locationYesThe location line on the profile page; empty when none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly and closed-world, and the description reinforces that with 'reads local files only' and describes the return shape (verdict plus level plus reason) even though no output schema exists. It also discloses a non-obvious behavioral caveat: omitted company/mutuals silently downgrade a removal to a skip. Some classification terms (e.g. 'rescue place', 'mission words') are left unglossed.

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 action and output, followed by decision rules and then the precondition caveat, so the agent hits the operative information first. The middle sentence is a long packed enumeration, but no sentence is filler.

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 7-parameter decision tool with no output schema, the description covers action, return value, decision rules, and a failure mode, which is nearly everything needed to call it correctly. Minor gaps remain around what the intermediate levels (spam, borderline, low) actually imply for downstream handling.

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 the baseline is 3, but the description goes further by explaining the functional role of specific inputs: company and mutuals gate bare-profile removal, headline and company drive spam detection, and name and degree drive the SKIP rules. That is genuine meaning beyond the field-level schema text.

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?

States a specific verb and resource: it compares the current profile page data against the stored connection and emits a REMOVE or SKIP verdict with level and reason. Very concrete, but it never names a sibling (e.g. connections_mark or connections_check_list) to distinguish when this verdict tool should be used instead of a mutation or listing tool.

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?

Provides explicit positive conditions for REMOVE (spam still in headline/company, sales-pitch headline, bare profile) and explicit exclusion conditions for SKIP (name mismatch, non-1st degree, rescue place or mission words, core or low level). It also states the preconditions for those rules to apply at all: company and mutuals must be passed or a bare profile is never removed.

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