Skip to main content
Glama

test_connectivity

Read-onlyIdempotent

Verify connectivity to the CERN GitLab instance and check authentication status, GitLab version, and connection health before running repository or CI/CD queries.

Instructions

Test connectivity to the CERN GitLab instance. Returns the GitLab version, authentication status, and connection health.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"test_connectivityArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "test_connectivityDictOutput",
      +  "type": "object"
      +}
  2. First observedv0.1.6

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered; the description adds value by disclosing the payload shape (GitLab version, authentication status, connection health). It stops short of saying what happens on failure — whether an unreachable host raises an error or returns an unhealthy status — which is the one behavioral detail an agent would still want.

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 short sentences with zero filler; the purpose is front-loaded and the return content follows. Nothing is repeated from the name or annotations, and every clause carries information.

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 zero-parameter probe with an output schema and full annotation coverage, the description supplies nearly everything needed to invoke it correctly. The remaining gap is a note about prerequisites (e.g., that a configured token determines the authentication status reported) and failure semantics.

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 tool takes zero parameters, so the schema-side baseline is 4 and there is nothing further for the description to document. No parameter meaning is missing or misrepresented.

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 names a specific action (test connectivity) against a specific resource (the CERN GitLab instance), and no sibling tool overlaps with that job — every sibling reads project, file, issue, or release data. An agent can tell immediately that this is the health/connection probe rather than a data-retrieval call.

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?

Usage is only implied: an agent can infer this is the right call to verify credentials or reachability before running other GitLab operations, but the description never says so explicitly. There are no stated exclusions, no mention of when a failure should route elsewhere, and no guidance on whether it should be called once per session or before every operation.

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