Skip to main content
Glama
Sign In
@takeokunn/metabase-mcp

@takeokunn/metabase-mcp

by takeokunn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_card_param_values

Search possible values for a saved question's filter parameter in Metabase to retrieve matching options based on a query string.

Instructions

Search possible values for a card (saved question) filter parameter in Metabase

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "search_card_param_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description should disclose behavioral traits. It does not mention that the operation is read-only, whether authentication is required, or any error conditions (e.g., invalid card ID).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 14 words, which is concise. However, it could be slightly improved by front-loading the primary action and including key constraints (e.g., card ID required).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description is incomplete. It does not specify the return format, pagination, or behavior when no values match. The tool has many siblings, but no guidance on differentiation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% per context, meaning the schema does not adequately describe parameters. The tool's description adds no explanation of the 'input' object's fields (id, param_key, query), leaving the agent to infer from the names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Search' and the resource 'possible values for a card (saved question) filter parameter'. It distinguishes from sibling tools like search_dashboard_param_values and search_dataset_param_values by specifying 'card'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool vs alternatives like search_dashboard_param_values or search_embed_card_param_values. The description lacks any when-to-use or when-not-to-use hints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools