Skip to main content
Glama

get_status

Check installed, configured, and working unlocker tiers, search providers, and platform integrations. Run first when another searchts tool fails or before relying on optional capabilities.

Instructions

Report the health of this searchts install: which unlocker tiers, search providers, and optional platform integrations are installed, configured, and working. Use this first when another searchts tool fails or before relying on an optional capability (e.g. keyed search providers, transcription). Takes no arguments and performs no web requests of its own beyond the cached update check; returns a plain-text report, one line per channel starting with ok, warn or error, never wrapped, so a fix command on its own indented line can be copied as-is. 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • addedInput schema / title
      Added value: +"get_status_toolArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {
      +      "title": "Result",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "title": "get_status_toolOutput",
      +  "type": "object"
      +}
  2. First observedv0.5.1

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden, and it does: no arguments, no web requests beyond a cached update check, exactly one GET to the named GitHub endpoint at most once per 24h cached in a named path, no user data in the request, nothing installed or changed, and an env var to disable it. This is unusually complete disclosure of side effects and constraints.

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 purpose, then usage guidance, then output format, then the update-check caveat – a sensible ordering. It is somewhat long and the update-check/exfiltration-assurance passage is dense, but each sentence carries distinct operational value (callability, output shape, network side effect).

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?

Although an output schema exists, the description still adds essential semantics the schema cannot: plain-text one-line-per-channel report with ok/warn/error prefixes, never wrapped, indented fix commands copy-ready as-is, and the optional update_available field. Combined with the network/side-effect disclosure, an agent has everything needed to call it and interpret results.

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?

Zero parameters, which is the baseline-4 case, and the description reinforces it ("Takes no arguments"), confirming the agent need not construct any input. No further parameter meaning is needed, so it stops short of 5 only because there is nothing extra to add.

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+resource ("Report the health of this searchts install") and enumerates what health means: unlocker tiers, search providers, platform integrations, each installed/configured/working. This clearly distinguishes it from siblings like login_status (auth only) and web_search (query execution).

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?

Explicit when-to-use: "Use this first when another searchts tool fails or before relying on an optional capability (e.g. keyed search providers, transcription)." Names concrete triggering conditions and future-facing intent, not just a vague hint.

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