Skip to main content
Glama

Mdexa

List categories and filter values

list_facets
Read-onlyIdempotent

Valid filter values for search_datasets with dataset counts: core facets and tag facets (not_enabled ones cannot filter yet). Pass only= to save tokens. Domains are a tree: depth=1 lists the top level, parent= one branch.

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": "list_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
onlyNo
depthNo
hintsNo
parentNo
tag_sourceNodeclared = only tags the authors state or a reviewer confirmed.any

Output Schema

NameRequiredDescriptionDefault
facetsNo
tag_facetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds substantive behavior beyond them: results carry dataset counts, some facets are returned but not yet usable for filtering, and token cost can be reduced via only=.

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?

Three short sentences, each carrying distinct information: return content, token-saving invocation, and tree navigation. The filter-count behavior is front-loaded and nothing is redundant.

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?

An output schema exists, so return-value detail is not required, and the description covers the one non-obvious output trait (per-facet counts, disabled facets). Coverage of the domain-tree parameters and the only= shortcut makes it callable without reading the schema closely; only the lang and hints parameters remain unaddressed.

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

Parameters4/5

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

Schema coverage is only 17%, so the description has to compensate — and it does for the three structurally important parameters: only= (narrows output to save tokens), depth=1 (top level of the domain tree), and parent=<domain> (one branch). The hints and lang parameters are left unexplained in both description and schema, which keeps it below a 5.

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

Purpose4/5

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

The description states precisely what the tool returns — valid filter values with dataset counts, split into core facets and tag facets — and names search_datasets as the consumer, so an agent can distinguish it from the search tool itself. It stops short of a clean verb-first statement ('Valid filter values...' is a noun phrase), but the resource and scope are unambiguous.

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

Usage Guidelines4/5

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

It establishes the workflow context (this supplies filter values for search_datasets) and gives explicit invocation advice with 'Pass only=<facet> to save tokens'. It also flags a real constraint: 'not_enabled ones cannot filter yet'. It never states when not to call this or that it should be called ahead of a search, leaving the sequencing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.