Skip to main content
Glama
ishay60

mcpolyglot

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
demo.list_tablesA

List all tables and their columns in the demo database.

demo.describe_tableA

Describe one table in the demo database, including columns, types, and primary key.

demo.queryA

Run a read-only SQL query against the demo database. Use parameterized form ($1, $2, ...). Writes are rejected.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: listing all tables, describing one specific table, and executing read-only queries. There is minor overlap in that list_tables also returns columns, but the boundary between the three is clear enough that an agent can reliably pick the right one.

Naming Consistency4/5

Names use a consistent snake_case verb_noun convention (describe_table, list_tables) with a uniform 'demo.' namespace prefix. demo.query is a slight deviation since it lacks a noun object, but it remains readable and clearly scoped.

Tool Count4/5

Three tools is on the lean side but appropriate for a deliberately read-only demo database exploration surface. Each tool earns its place without redundancy.

Completeness4/5

List, describe, and query cover the core read-only exploration lifecycle with no dead ends, since arbitrary queries can retrieve counts, samples, and joins. A few conveniences (e.g., a schema-wide search or sample-row helper) are absent but easily worked around via query.

Maintenance

ActivityMaintained
ResponsivenessNo issues