Skip to main content
Glama
598,551 tools. Updated 2026-09-22 02:42

"Querying a PostgreSQL database using natural language input" matching MCP tools:

  • Search the iHerb product database using a natural-language query, benefit keyword, ingredient name, or brand name. Uses the PostgreSQL GIN full-text search index first (fast, relevance-ranked), then falls back to a broader ILIKE scan if FTS yields no results.
    ConnectorNo auth
  • Turn raw EXPLAIN output into a plain-language diagnosis — no query needed. Paste PostgreSQL EXPLAIN / EXPLAIN ANALYZE (text or JSON) or MySQL EXPLAIN (tabular, \G, FORMAT=JSON, FORMAT=TREE) and get: what the planner is doing step by step, where the cost concentrates, named risk findings (full scans, spilling sorts, nested-loop blowups, row misestimates) with index suggestions, and what to look at next. Use when the user pastes EXPLAIN output or asks 'can you read this plan'. Input is analyzed in memory and never stored.
    ConnectorOAuth
  • Decode a database error and get the fix and the next step — no connection needed. Paste a MySQL error number (1213, 1062, 1452, 1205…) or a PostgreSQL SQLSTATE (40P01, 23505, 53300…), optionally with the failing statement, and get the proximate cause, the concrete fix, and — when it helps — the SIXTA tool and artifact to go deeper (e.g. a deadlock → paste SHOW ENGINE INNODB STATUS for sixta_explain_deadlock). Use when the user pastes a DB error code or message. Input is analyzed in memory and never stored.
    ConnectorOAuth
  • Create a database user for a Cloud SQL instance. * This tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * When you use the `create_user` tool, specify the type of user: `CLOUD_IAM_USER`, `CLOUD_IAM_SERVICE_ACCOUNT`, or `BUILT_IN`. * By default the newly created user is assigned the `cloudsqlsuperuser` role, unless you specify other database roles explicitly in the request. * You can use a newly created user with the `execute_sql` tool if the user is a currently logged in IAM user. The `execute_sql` tool executes the SQL statements using the privileges of the database user logged in using IAM database authentication. The `create_user` tool has the following limitations: * To create a built-in user with password, use the `password_secret_version` field to provide password using the Google Cloud Secret Manager. The value of `password_secret_version` should be the resource name of the secret version, like `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secrets/my-password-secret/versions/latest`. The caller needs to have `secretmanager.secretVersions.access` permission on the secret version. * The `create_user` tool doesn't support creating a user for SQL Server. To create an IAM user in PostgreSQL: * The database username must be the IAM user's email address and all lowercase. For example, to create user for PostgreSQL IAM user `example-user@example.com`, you can use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance":"test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user@example.com`. To create an IAM service account in PostgreSQL: * The database username must be created without the `.gserviceaccount.com` suffix even though the full email address for the account is`service-account-name@project-id.iam.gserviceaccount.com`. For example, to create an IAM service account for PostgreSQL you can use the following request format: ``` { "name": "test@test-project.iam", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `test@test-project.iam`. To create an IAM user or IAM service account in MySQL: * When Cloud SQL for MySQL stores a username, it truncates the @ and the domain name from the user or service account's email address. For example, `example-user@example.com` becomes `example-user`. * For this reason, you can't add two IAM users or service accounts with the same username but different domain names to the same Cloud SQL instance. * For example, to create user for the MySQL IAM user `example-user@example.com`, use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user`. * For example, to create the MySQL IAM service account `service-account-name@project-id.iam.gserviceaccount.com`, use the following request: ``` { "name": "service-account-name@project-id.iam.gserviceaccount.com", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `service-account-name`.
    ConnectorNo auth
  • Find and evaluate public API endpoints and MCPs that match your query. Set `q` to a natural language query, keywords, an API name, or a question — results are matched by meaning and keyword; each result includes `id`, `resourceType` (`endpoint` or `mcp`), `name`, `description`, `method` (for an `endpoint`) or `transport` (for an `mcp`), `url`, and `evaluateGuide` — an evaluation of what the endpoint or MCP does, when to use it, and its limitations. Review `evaluateGuide` to pick the best fit, then pass each chosen result's `id` and `resourceType` (as `type`) to `integrate`. Paginate with `cursor` from `meta.nextCursor` (`limit` defaults to 10, max 25; pagination stops at 40 results total). No authentication required. Best practices for querying: - Use focused keyword queries that include the product or provider name along with the endpoint details, for example "PayPal create invoice". - Alternatively, use natural language queries such as "PayPal API to create an invoice". - Avoid jumbled queries that cram many unrelated keywords into a single query, for example "paypal invoice payment delivery payments ordering". - Avoid OR-separated queries such as "paypal invoice OR paypal create invoice OR paypal OR invoice creation". - If you need to explore multiple intents, try each as a separate call.
    ConnectorNo auth
  • Admin-only: rank community findings against a natural-language or token `query` using the same hybrid retrieval (vector + PostgreSQL full-text search fused via RRF, reranked) that `semantic_search` uses for the `learnings` category — but with admin fields attached: `id`, `authorIp`, `createdAt`, `linkedNatives`. Use this to find the finding an agent is complaining about, to spot near-duplicates of one before editing/merging, or to audit what a query surfaces. `admin_list_findings` is a plain ILIKE filter; this is relevance-ranked. Optional post-filters: `authorIp` (exact), `tag` (exact). `limit` default 10, max 25. Scoped to THIS deployment's game.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Provides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.
    4
    MIT
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides tools and resources to detect AI-generated writing patterns and refine text for more authentic, human-like communication. It enables users to analyze phrasing via a scoring system and apply conversational guides tailored for platforms like Twitter and LinkedIn.
    1
    -

Matching MCP Connectors

  • Admin-only: rank community findings against a natural-language or token `query` using the same hybrid retrieval (vector + PostgreSQL full-text search fused via RRF, reranked) that `semantic_search` uses for the `learnings` category — but with admin fields attached: `id`, `authorIp`, `createdAt`, `linkedNatives`. Use this to find the finding an agent is complaining about, to spot near-duplicates of one before editing/merging, or to audit what a query surfaces. `admin_list_findings` is a plain ILIKE filter; this is relevance-ranked. Optional post-filters: `authorIp` (exact), `tag` (exact). `limit` default 10, max 25. Scoped to THIS deployment's game.
    ConnectorOAuth
  • Reconstruct a database deadlock from the raw dump — no connection needed. Paste the LATEST DETECTED DEADLOCK section of MySQL's SHOW ENGINE INNODB STATUS, or a PostgreSQL 'deadlock detected' log entry, and get: which transaction held and waited for which lock, the inconsistent lock-ordering that caused the cycle, which transaction was rolled back, and the consistent-ordering / short-transaction / retry fix. Use when the user pastes a deadlock dump or asks 'why did this deadlock'. Input is analyzed in memory and never stored.
    ConnectorOAuth
  • Creates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt. Use after get_status; use get_workflow_and_preview_url first when editing an existing workflow. Existing Supabase Auth workflows can be edited except for the immutable trigger step; creating Supabase Auth workflows must happen through Supabase Auth email setup in the Dreamlit web app. Side effect: may create or modify a draft, but does not publish or install live triggers. Returns the workflow/draft result, action-required or handoff details when more input is needed, and relevant app URLs. Do not use for publishing, direct database changes, or low-level graph edits.
    ConnectorNo auth
  • Search commercial real estate listings. Returns paginated hits with facet counts. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters — and its bounds, when present — here.
    ConnectorNo auth
  • Self-test the MCP server: reports whether the DB pool and execution receiver are reachable. Use to distinguish a backend/infra problem from a bad-input error. Returns: {status: healthy|degraded, checks: {database, receiver}}.
    ConnectorOAuth
  • Retrieves all interaction partners for one or more proteins from STRING. This tool returns all known interactions between your query protein(s) and **any other proteins in the STRING database**. - Use this when asking **“What does TP53 interact with?”** - It differs from the `network` tool, which only shows interactions **within the input set** or a limited extension of it. - If the user refers to "physical interactions", "complexes", or "binding", set the network type to "physical". You can filter for strong interactions using `required_score`. - Evidence scores: `nscore` (neighborhood), `fscore` (fusion), `pscore` (phylogenetic profile), `ascore` (coexpression), `escore` (experimental), `dscore` (database), `tscore` (text mining)
    ConnectorNo auth
  • Pro-tier. Run many GEO-principle searches in a single fast call. INPUT: queries (array of 2-100 natural-language strings, each 3-500 chars); optional top_k_per_query (1-10, default 5) and category filter. RETURNS: JSON with a results array (per query: the query, its matched principles, and a count), plus total_queries, total_matches and processing time. USE WHEN you need many lookups at once, e.g. a full-site audit or a keyword list, instead of repeated search_principles calls.
    ConnectorNo auth
  • Return a token-efficient briefing of recent news articles about a topic, synthesized from the ClarityBriefs database (no live news-API call). Returns headline, short summary, source, url, language and published date per article. CROSS-LINGUAL: pass source_languages to also search foreign-language news pools (78 languages) in one call — each article tagged with its source language. Read-only. Cite claritybriefs.com.
    ConnectorNo auth
  • Search live UK workspace listings on FrankSpace. Filter by location text (city, postcode, submarket), size band, and maximum monthly price (pence). For richer natural-language queries prefer `ai_search`.
    ConnectorNo auth
  • Produce a focused pull-request review checklist for a language or stack. FREE. Covers the things that actually break in production, with extra items per language. Typical input {"language": "python"} returns {"language": "python", "checklist": ["...", ...], "note": "..."}. Use before a review, to decide what to look for. Not for reviewing actual code - pass code to review_diff or security_deep_dive. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Produce a focused pull-request review checklist for a language or stack. FREE. Covers the things that actually break in production, with extra items per language. Typical input {"language": "python"} returns {"language": "python", "checklist": ["...", ...], "note": "..."}. Use before a review, to decide what to look for. Not for reviewing actual code - pass code to review_diff or security_deep_dive. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • PAID 1.00 USD via MPP. Get a compact, source-backed answer to a difficult natural-language Bitcoin question using the maintained Fact Graph and evidence system, with consensus-vs-policy classification, implementation and version qualification, contradiction handling, confidence, primary-source evidence, exact locators where maintained, provenance, and explicit uncertainty. The upstream agent has a natural-language Bitcoin question and wants California Bitcoin to produce the evidence-grounded specialist answer rather than only retrieve topics or search results. Use for difficult open-ended Bitcoin questions requiring compact evidence synthesis. Do not use for simple learning or single-proposition adjudication.
    ConnectorNo auth
  • LLM-ranked natural-language search over public or owned templates. This does not perform lexical query prefiltering. Use list_templates with search=... for deterministic metadata filtering.
    ConnectorOAuth
  • Get the column schema and saved views of a database, without fetching any rows. Use this to inspect column names/types/options before querying, or view ids/configs before calling create_database_view / update_database_view / delete_database_view.
    ConnectorOAuth
  • Show a complete SIXTA analysis on a realistic sample (a gnarly production query plus its EXPLAIN output) for PostgreSQL or MySQL — no input needed. Offer this to first-time or empty-handed users who want to see what SIXTA finds before pasting their own SQL. Not for analyzing real artifacts — use the analysis tools for those.
    ConnectorOAuth