Skip to main content
Glama

get_catalog_facets

Read-only

Discover available exact task tags and kinds with item counts. Optional kind limits all counts.

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

Input Schema

NameRequiredDescriptionDefault
kindNo

Output Schema

NameRequiredDescriptionDefault
tagsYes
kindsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds that returned data includes 'item counts', which explains why results are dynamic and consistent with idempotentHint=false, but it says nothing about scope (whole catalog vs. filtered), freshness, or cost of an open-world call.

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?

Two short sentences, front-loaded with the purpose and followed by the parameter note; no filler. Minor deduction because 'exact task tags' is compressed enough to be ambiguous for a first-time reader.

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

Completeness3/5

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

With an output schema present, return-value explanation is not required, and annotations cover the safety profile. Still missing for a discovery tool: the scope of the counts and whether this should be called before searching, which an agent needs to sequence it correctly.

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 description coverage is 0%, so the description must compensate; it does clarify that the single 'kind' parameter is optional and that it narrows all counts, which is genuine meaning beyond the bare enum. It does not explain what the seven enum values (skill, cli, mcp_collection, etc.) represent or whether filtering removes facet categories entirely.

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?

States a specific verb and resource: 'Discover available exact task tags and kinds with item counts.' An agent can tell this is a facet-enumeration tool rather than an item fetch like get_catalog_item. The phrase 'exact task tags' is slightly opaque jargon and no sibling is named for contrast, keeping it below a 5.

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?

The only guidance offered is about the optional parameter ('Optional kind limits all counts'), not about when to call this versus search_catalog or get_catalog_item. There is no stated prerequisite or exclusion; the agent must infer that this is a pre-search discovery step.

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.

Resources