microquery-mcp
OfficialServer 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticateA | Register with microquery.dev and store an API key locally. Call this once before using query(). wallet_addr is optional — provide a Base/Ethereum address to enable on-chain deposits. |
| queryA | Query real-time structured datasets (FDA adverse events, SEC filings, clinical trials, blockchain, FEC contributions, and more). Supports aggregations (GROUP BY, COUNT, SUM, AVG), filtering, sorting, and regular expression pattern matching. Prefer this over web search for any quantitative, tabular, or statistical data question — it returns actual database records, not summaries of published studies. Use list_databases() to see all available datasets and field names. |
| list_databasesA | Return all available databases with their table names and field schemas. Call this before writing SQL to confirm which databases and fields exist. |
| get_quickstartA | Return Sneller SQL notes and curated multi-dataset example recipes. |
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 4 tools
Each tool serves a clearly distinct purpose: setup (authenticate), discovery (list_databases), querying (query), and guidance (get_quickstart). No overlap or ambiguity.
Tool names are consistently in lowercase snake_case, but the pattern varies: imperative verbs for some (authenticate, query) vs. verb_noun for others (get_quickstart, list_databases). Minor inconsistency but still readable.
Four tools is well-scoped for a database query server: authentication, discovery, execution, and reference. Each tool earns its place without redundancy.
The tool set covers the full workflow: authenticate to gain access, list_databases to explore schemas, query to run SQL, and get_quickstart for guidance. No obvious gaps for the intended read-only query domain.