Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Openapi Server Info

openapi_server_info

Check MCP server connectivity, identity, health, token status, and registered tools using live in-process diagnostics, with no external API calls.

Instructions

Call this tool whenever the user asks:

  • "are you connected to openapi?" / "sei connesso a openapi?"

  • "which server / instance is running?"

  • "what is your status?" / "are the tools working?"

  • any question about connectivity, health, or identity of this MCP server.

Returns live diagnostic data directly from the running process — no external API calls are made. The response includes:

  • server name, version, and mode (sandbox vs production)

  • instance identity: user@hostname, PID, and startup timestamp so different running instances (local dev, staging, Cloud Run) are immediately distinguishable

  • token status: whether OPENAPI_TOKEN / OPENAPI_SANDBOX_TOKEN are set in the server environment, with a masked preview of the active token

  • list of all MCP tools currently registered and available

  • session identifiers for the current request

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does it well: it states no external API calls are made, lists exactly what the response contains, and warns that environment tokens are reported with a masked preview, which is security-relevant context an agent would otherwise not know. It stops short of explicitly declaring the operation read-only and non-destructive, which is why it is not a 5.

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?

The trigger phrases are front-loaded and the return contents are bulleted, so the structure scans well. It runs somewhat long with several near-duplicate multilingual trigger examples, but each line maps to a real disambiguation need.

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?

There is no output schema, so the description must explain return values, and it enumerates all response fields (server name/version/mode, instance identity, token status, registered tools, session ids). Nothing an agent needs to interpret the result correctly is missing.

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 zero parameters, so the schema fully specifies the input contract and the description has nothing to add. Baseline for a parameterless tool applies.

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 states a specific verb and resource: it returns live diagnostic data from the running MCP server process, covering identity, token status, and registered tools. This is clearly distinct from every sibling tool, which performs external data lookups (company, address, email checks), so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit, quoted user utterances that should trigger the call ('are you connected?', 'which server is running?', 'are the tools working?') plus a general rule covering connectivity, health, and identity questions. No sibling performs an overlapping function, so the omission of a named alternative is not a gap.

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