VAIA filtered data queries fail with API-1013 Invalid filter string via the MCP fetchClarityData tool
search cancel

VAIA filtered data queries fail with API-1013 Invalid filter string via the MCP fetchClarityData tool

book

Article ID: 454477

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

When a Clarity AI Agent runs a data query that needs a filter, the MCP fetchClarityData tool runs without the wrapping parentheses the filter grammar requires so the call fails with API-1013 and the agent returns no rows.

STEPS TO REPRODUCE:

  1. Connect to an environment with Vaia enabled
  2. Create a new AI Agent with Type Project, Context Object Chat panel, Tool enabled Yes, Allow User Input Yes
  3. Set the agent prompt to the text below
    • You are a Clarity PPM assistant for the Project "$[object.name]". Help the user with questions about this project's tasks, staff and status. Use the Clarity MCP tools for live data: describeClarityObjects, then describeClarityAttributes/getClarityApiSpec, then lookupClarityValues to resolve names to internal IDs, then fetchClarityData. Never guess an id, code or attribute name.
  4. Go to a project, open the the VAIA chat for Project Object, and ask "list open tasks on project PR1001"

Expected Results: A filtered agent query such as active projects returns the matching rows.

Actual Results: The query returns no rows and the tool call fails with API-1013 "Invalid filter string ... Each expression must start and end with parentheses". The same query with the filter already wrapped returns rows normally.

Environment

Clarity 16.4.3

Cause

DE211460

Resolution

In Review by Engineering