Skip to main content
Glama
Sign In

Vitalli

by app.vitalli.mcp
OverviewDiscussionsAdmin

vitalli_connection_status

Read-onlyIdempotent

Diagnostics for this connection: gateway build (commit, build time), server time, the apps the user has enabled for AI access, and the complete list of tool names the gateway serves for this account right now. An MCP client fetches the tool list once when connecting, so this list can contain tools that a long-running client does not show yet. Also returns reportHeader, a one-line statement (German) of the gateway build and query time that a test note or bug report can be dated with.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real value beyond them: the MCP client fetches the tool list once at connect time so this list may contain tools a long-running client doesn't show, and reportHeader is specifically German-language. It does not mention auth or rate limits, but for a read-only diagnostics call that is minor.

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?

Content is front-loaded with the diagnostics summary before the caveat and the reportHeader note. Each sentence carries information, though the reportHeader sentence is somewhat long and could be tightened without losing its point.

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, the description must enumerate return values, and it does so completely: build commit and time, server time, enabled apps, the full tool-name list, and reportHeader. The caching caveat and language note preempt the two most likely misreadings of 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?

The tool takes zero parameters, so the baseline is 4; the description correctly describes only outputs and makes no parameter claims that could mislead.

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 verb+resource ('Diagnostics for this connection') and enumerates exactly what is returned: gateway build, server time, enabled apps, and the served tool list. This is unmistakably distinct from the sibling tools, which are all domain CRUD operations on contacts, plans, or health data.

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

Usage Guidelines4/5

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

It establishes the usage context clearly: diagnostics/debugging, and dating a 'test note or bug report' with reportHeader. It also warns about the tool-list caching caveat when interpreting results. It stops short of explicit when-not-to-use or naming an alternative tool, so it is a 4 rather than a 5.

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

All Vitalli toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources