CenuFiltrs Price Comparison

Get CenuFiltrs Search Facets

cf_search_facets

Read-onlyIdempotent

Get available search filters (brands, categories, price range) for a query. Each category comes back with the ltree path that cf_search_offers.categories expects. Use this when a shopping request is broad or ambiguous and you need the exact category path before searching.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cf_search_facets"
  }
}

Input Schema

Name	Required	Description
`q`	No	Search query to get facets for
`brands`	No	Current brand filter
`categories`	No	Current category filter

Output Schema

Name	Required	Description	Default
`links`	Yes
`query`	Yes
`facets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds behavioral context by specifying that facets are query-dependent and that category paths come in ltree format for integration with cf_search_offers. It does not contradict annotations and covers key behavior beyond the safety profile.

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?

The description is exactly two sentences, front-loaded with the tool's action and followed by a clear usage rationale. Every word contributes value, with no redundancy or filler.

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?

The tool is simple, has an output schema, and strong annotations. The description covers the essential purpose, integration nuance (ltree), and usage context. It lacks explicit behavior for edge cases like empty queries, but that is likely handled by schema and output schema, so overall completeness is high.

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 100% with descriptive parameter descriptions, so the baseline is 3. The description only adds a subtle nuance by calling brands/categories 'current filters,' implying they constrain facets, but this is marginal. No significant extra meaning is provided beyond the schema.

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 tool retrieves search facets (brands, categories, price range) for a query. It explicitly differentiates from siblings by noting the ltree 'path' for cf_search_offers.categories, making its role and output specific.

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?

The description provides an explicit usage trigger: 'Use this when a shopping request is broad or ambiguous and you need the exact category path before searching.' This not only tells when to use the tool but also implies when to defer to cf_search_offers, giving clear alternative guidance.

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

All CenuFiltrs Price Comparison 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?