Informix MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tablesB | Get all tables in the database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get-tables' has a clearly distinct and singular purpose, making it impossible for an agent to misselect between multiple options.
The naming follows a consistent verb_noun pattern with 'get-tables', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable within this minimal set.
A single tool for a database server is too few for the apparent scope, as it lacks basic CRUD operations, querying, or other database management functions. This severely limits the server's utility and feels incomplete for a database domain.
The tool surface is severely incomplete for a database server, covering only table listing without any operations for data retrieval, insertion, updates, deletions, schema modifications, or other essential database interactions. This creates significant gaps that will cause agent failures in typical database workflows.