Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

check_connection

Read-onlyIdempotent

Verify which VAN committee and database the server is connected to and confirm whether write tools are enabled.

Instructions

Which VAN committee and database this server is connected to, and which write tools are on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context: that write tools can be toggled on or off and that the tool reveals that state, which matters for planning later calls. It stops short of saying whether it validates live connectivity or surfaces auth/error state.

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?

One compact sentence with no filler; the environment details come first and the write-tool capability second. The phrasing 'which write tools are on' is slightly colloquial and would read better as an explicit verb clause, but nothing is wasted.

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 diagnostic tool with an output schema and full annotation coverage, the description supplies what is needed to decide to call it and what kind of state it reveals. Only the activation condition ('call this first / on connection errors') is left unstated.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The input schema is a closed empty object, matching the description's implication that the call is unconditional.

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?

The description names the concrete information returned: the VAN committee, the database, and which write tools are enabled on the server. It is a noun phrase rather than a verb-led statement ('Report/Return ...'), but the resource and scope are unmistakable and clearly distinct from the data-query siblings. The only gap is the absence of an explicit action verb.

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?

Use is only implied: an agent can infer it should call this to verify environment or confirm write capability before mutating data. There is no explicit statement of when to call it, no prerequisites, and no naming of alternatives, though with zero parameters and a distinct purpose the alternatives are largely self-evident.

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