Skip to main content
Glama
Sign In
x-mcp

x-mcp

by LesterAJohn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

x_connection_info

Retrieve X MCP runtime metadata, inventory source, Postgres and Vault connection settings, and auth-gate state to diagnose configuration and connectivity issues.

Instructions

Return X MCP runtime metadata, inventory source, Postgres/Vault connection settings, and auth-gate state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Return' implies a read-only operation, but it doesn't explicitly state that there are no side effects, nor does it mention authentication requirements, rate limits, or potential errors. The list of returned information adds some transparency, but it is not comprehensive.

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?

The description is a single, front-loaded sentence that lists all information categories without redundancy or unnecessary detail. It is concise and well-structured.

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?

The description enumerates what the tool returns, but terms like 'inventory source' and 'auth-gate state' are not defined, and no return format is mentioned. Given the lack of an output schema, this introduces some ambiguity, but the overall context is adequate for a zero-parameter diagnostic tool.

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 input schema has zero parameters, so there is nothing to explain. The description adds value by detailing the output categories, which is the relevant semantic content for this tool. Baseline 4 applies for 0-parameter tools.

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 uses the specific verb 'Return' and enumerates the exact categories of information (runtime metadata, inventory source, Postgres/Vault connection settings, auth-gate state), clearly distinguishing it from siblings like x_health_check or x_config_list.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as x_health_check or x_config_get. The description only states what it returns, with no mention of use cases or exclusions.

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