Skip to main content
Glama
Sign In
Clonst

Clonst

by capritora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clonst_ping

Diagnose server health, verify Codex CLI availability and version, check login status and config, and access logs without consuming LLM quota.

Instructions

Full Clonst server diagnostic: health, codex CLI availability and version, login status, loaded config, logs directory. Consumes no LLM quota.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool consumes no LLM quota and lists the diagnostic checks, but does not specify if there are side effects or network calls.

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

Conciseness5/5

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

Two sentences: first efficiently lists the diagnostics, second adds the notable quota information. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains what the tool checks but not what it returns (e.g., health status format). Given no output schema, more detail on the response would improve completeness.

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?

There are no parameters, so the baseline is 4. The description adds value by explaining the tool's purpose, which is sufficient given no parameters are needed.

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 description clearly states 'Full Clonst server diagnostic' and lists specific aspects it checks (health, codex CLI availability and version, login status, loaded config, logs directory), distinguishing it from siblings that are summary/review tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'Consumes no LLM quota' implying it's safe to use freely, but lacks explicit guidance on when to use this tool instead of siblings like clonst_report_summary or clonst_review.

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

Deploy Server

Other Tools