Quattr

find_relevant_analysis

Read-only

Route an analytics question to the authoritative Quattr analysis — returns the best-matching analysis tool(s), why, and how to call them. Call this FIRST for every analytics question unless the user explicitly named the exact tool; use content discovery only when this router reports that no dedicated analysis fits.

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": {
      "question": "<question>"
    },
    "name": "find_relevant_analysis"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`present`	No	Set true ONLY when the user wants the list of matching analyses AS the answer (renders a suggestions card). OMIT when routing to an analysis you will then call — routing must not paint a card before the answer.
`question`	Yes	the analytics question in the user's words

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds genuine behavioral value by disclosing what the tool returns (matching tools, rationale, invocation guidance) and that it functions as a router rather than an executor. It does not describe the limit/pagination behavior, keeping it below a 5.

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

Conciseness5/5

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

Two tight sentences with no waste, front-loading the routing purpose before the conditional fallback. Every clause earns its place.

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

Completeness4/5

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

There is no output schema, and the description compensates by stating what is returned (best-matching tool(s), why, how to call them). For a routing tool this is nearly complete; only the limit/pagination behavior and card-rendering interaction are left to the schema.

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

Parameters3/5

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

Schema coverage is 67%, so the schema documents most parameters (including a rich description for 'present'). The description adds no parameter-level guidance of its own — notably silent on the 'limit' parameter, which has no schema description.

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?

States a specific verb (route) and resource (analytics question to authoritative Quattr analysis), plus what it returns (best-matching tool(s), why, how to call them). This clearly distinguishes it from the sibling find_relevant_content, which handles content rather than analyses.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('Call this FIRST for every analytics question unless the user explicitly named the exact tool') and names the alternative with its triggering condition ('use content discovery only when this router reports that no dedicated analysis fits'). Both the positive and negative cases are covered.

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

All Quattr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?