Skip to main content
Glama

login_check

Checks whether saved cookies can access a signed-in-only page once and reports logged in, logged out, or unknown; use it to verify a login wall is absent.

Instructions

Read one signed-in-only page with the saved cookies, once, and say 'logged in', 'logged out' or 'unknown'. Direct requests only: the cookies and URL are never sent to the Jina relay. It proves a login wall is absent, not which account is signed in, and an expiry is only an upper bound. A captcha, block or network error is 'unknown', never a guess. For reddit.com, linkedin.com, github.com and x.com a known account page is used; other sites need a signed-in-only URL, and a public page is reported as 'unknown' because it proves nothing about the account. check_url checks a custom signed-in-only page instead of the known one; the cookies still come from url's site. An invalid url is an error result carrying the usual JSON error envelope, not an 'unknown' login answer. Update check: when a newer release exists, a successful result also carries 'update_available' plus, at most once per 24 hours, one line telling the agent. The check is one GET to the GitHub latest release of capad-xyz/searchts, at most once per 24 hours, cached in ~/.searchts/update-check.json, with a searchts User-Agent and nothing about the user. Nothing is installed or changed. SEARCHTS_NO_UPDATE_CHECK=1 turns the check and the note off.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
check_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "login_check_toolOutput",
      -  "type": "object"
      -}New value: +null
  2. Addedv0.22.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that cookies/URL are never sent to the Jina relay, that the result proves only the absence of a login wall and not which account is signed in, that an expiry is only an upper bound, and that captcha/block/network errors map to 'unknown' rather than a guess. It also describes the error path for an invalid url and the update-check side effect in detail (one GET to GitHub's latest release, 24h cache at ~/.searchts/update-check.json, searchts User-Agent, nothing installed, SEARCHTS_NO_UPDATE_CHECK=1 to disable).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the purpose and output vocabulary, which is good, but the closing update-check material runs several sentences and is mostly release-infrastructure detail that outweighs the core login semantics in length. Dense and information-rich, yet the proportional weight given to a tangential concern costs it.

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?

With no output schema and no annotations, the description still covers the return values, the error envelope for a malformed url, the site-specific behaviors, the ambiguity cases, and an extra field (update_available) that can appear on a successful result. An agent has everything needed to call it and interpret the response.

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 0%, so the description must compensate, and it does for check_url: it explains that check_url substitutes a custom signed-in-only page while the cookies still come from url's site. For url itself the meaning (the site whose saved cookies are used) is only implied indirectly via 'the cookies still come from url's site' and the invalid-url error case, which is slightly indirect for the required parameter.

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?

The first sentence states a specific verb+resource and the exact three-valued answer: read one signed-in-only page with saved cookies and return 'logged in', 'logged out' or 'unknown'. It also carves out scope relative to siblings ('check_url checks a custom signed-in-only page instead of the known one'), so the agent can distinguish it from login_status and read_url without opening any schema.

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 when-to-use (sites with known account pages: reddit.com, linkedin.com, github.com, x.com) and when-not (public pages reported as 'unknown' because they prove nothing; other sites need a signed-in-only URL passed via check_url). It names the alternative tool and the exact condition that selects it, so no inference is required.

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