Lists column details from a specific table in a legacy MySQL database using SHOW FULL COLUMNS. Provides read-only schema inspection for databases on MySQL 5.0–5.6.
Lists columns with SHOW FULL COLUMNS FROM .. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| table | Yes | ||
| database | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description is the only source of behavior. It states read-only, which is helpful, but lacks details like whether it requires specific privileges or what the output format is.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very concise, one sentence front-loaded with intent. No wasted words, though it could be slightly more detailed within the same space.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations, no output schema, and minimal parameter documentation, this description is incomplete. It fails to mention output structure, prerequisites, or any edge cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description does not explain the parameters beyond naming them. An agent gets no additional meaning for database or table beyond their names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists columns via SHOW FULL COLUMNS for a specified database and table, distinguishing it from siblings like list_tables and show_create_table.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. It implies use for column information, but doesn't contrast with show_create_table or list_indexes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.