Skip to content

Looker MCP handles filter incorrectly when value is a string with a comma #1790

@MarkPare

Description

@MarkPare

Prerequisites

  • I've searched the current open issues
  • I've updated to the latest version of Toolbox

Toolbox version

0.17.0

Environment

  1. Linux amd64
  2. How are you running Toolbox:
  • As a container from central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:0.17.0

Client

  1. Client: Claude web
  2. Version: latest

Expected Behavior

It handles filter by a string value correctly.

Current Behavior

I'm using Claude with Looker MCP and seeing cases where Claude submits a query that looks correct but the actual SQL that Looker MCP processes is not correct. Specifically, in the case shared below, the looker query has a filter for "markets.name: New York, NY" which should return results for my data, but when asking Claude to share the actual SQL used by Looker MCP, I can see that it is generating the SQL as a fieldName IN filter, which is not correct and causing no results to be returned.

Is this expected behavior by Looker MCP to take a string with commas and treat it as a list instead of a single string?

Steps to reproduce?

Looker query from Claude:

{
  `limit`: 100,
  `model`: `my_model`,
  `fields`: [
    `clients.name`,
    `orders.count`
  ],
  `explore`: `my_orders`,
  `filters`: {
    `markets.name`: `New York, NY`,
  }
}

Sql query run by Looker MCP:

SELECT
    ...
FROM
    ...
WHERE 
    "markets"."name" IN ('New York', 'NY')
LIMIT 100

Additional Details

No response

Metadata

Metadata

Labels

type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.type: questionRequest for information or clarification.

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions