ET-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QDRANT_URL | No | Qdrant storage URL. A local directory will be auto-created if not set. | .qdrant_storage |
| DB_ROW_LIMIT | No | Maximum number of rows returned per query. | 500 |
| SUPABASE_DB_URL | No | PostgreSQL connection string for catalog tools (read-only). Required only when using the catalog server or the 'all' server with catalog functionality. | |
| DISABLE_SITE_VECTOR | No | Set to 'true' to disable vector search for the site server and use BM25+grep only. | true |
| SITE_MIN_CONFIDENCE | No | Minimum confidence threshold for site knowledge base search results. | 0.35 |
| EMBEDDING_MODEL_NAME | No | Embedding model used for optional vector stages. | BAAI/bge-small-en-v1.5 |
| DB_STATEMENT_TIMEOUT_MS | No | Per-query timeout for database operations in milliseconds. | 8000 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_calculatorA | Find optics calculators for a natural-language question. → get_calculator → calculate. |
| get_calculatorA | Get inputs, gotchas, related calculators for a formula_id. Call after search_calculator. |
| calculateB | Execute a calculator. Flow: search_calculator → get_calculator → calculate. |
| search_lookupsC | Find reference/lookup tables (sensor sizes, f-stops, pixel formats). → get_reference → lookup. |
| get_referenceA | Get a lookup table's purpose, keys, notes. Call after search_lookups. |
| lookupC | Retrieve one value from a reference table. |
| search_knowledge_baseB | Search EarthTekniks KB (company, platforms, projects, vision fundamentals). Returns ranked snippets + confident flag. |
| get_documentA | Read full text of a KB document by doc_id. |
| list_familiesB | List lens families and their tables. |
| list_tablesC | List catalog tables with purpose. Optional family filter. |
| describe_tableA | Describe a table: columns, purpose, signature columns. Call before run_select. |
| search_knowledgeC | Find which table/family fits a use-case NL question. → get_table_knowledge. |
| get_table_knowledgeB | Full knowledge for a table: purpose, column meanings, NL->SQL examples, gotchas. |
| lookup_modelB | Find which table/family a lens model belongs to. |
| get_productB | Get full spec row(s) for a lens model. |
| search_productsC | Filtered search over one table or family. filters: [{column, op, value}]. |
| run_selectB | Run a validated read-only SELECT. |
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 17 tools
The set has several similarly named tools, especially search_knowledge vs search_knowledge_base and lookup vs lookup_model, which could cause misselection. However, the descriptions include distinct target objects and explicit workflow arrows (search → get → execute) that mostly help an agent separate calculators, lookups, tables, and products.
Most tools follow a consistent verb_noun snake_case pattern such as get_document, search_products, list_tables, and describe_table. The main deviations are the bare verbs calculate and lookup, plus the confusingly parallel search_knowledge and search_knowledge_base names.
At 17 tools, the server sits in the heavy range and feels padded by the repeated search → get → execute triads for calculators, lookups, and table knowledge. Each tool does have a distinct role, but the count is borderline for smooth agent navigation.
The read-only surface covers the main domains: KB documents, calculators, reference lookups, product specs, and catalog SQL queries with no obvious dead ends. Minor gaps exist—like no browse-all for calculators or lookups and no document listing—but the search tools provide workable entry points.