Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Catalogs

list_catalogs
Read-only

Retrieve and filter Rootly catalogs by name, slug, managed-by, external ID, or date; control sorting, pagination, and included fields or entities.

Instructions

List catalogs

Input Schema

NameRequiredDescriptionDefault
sortNocomma separated if needed. eg: created_at,updated_at
includeNocomma separated if needed. eg: fields,entities
page_sizeNo
filter_nameNo
filter_slugNo
page_numberNo
filter_searchNo
filter_name_eqNo
filter_name_inNo
filter_slug_eqNo
filter_slug_inNo
filter_managed_byNo
filter_external_idNo
filter_name_not_eqNo
filter_name_not_inNo
filter_slug_not_eqNo
filter_slug_not_inNo
filter_created_at_gtNo
filter_created_at_ltNo
filter_managed_by_eqNo
filter_managed_by_inNo
filter_created_at_gteNo
filter_created_at_lteNo
filter_managed_by_not_eqNo
filter_managed_by_not_inNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

D1.6/5.0
Behavior2/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 the safety profile is covered. The description contributes nothing beyond that – no pagination behavior, no default sort, no note on what 'include' expands to.

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

Conciseness2/5

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

Extremely short, but this is under-specification rather than conciseness. Two words cannot front-load meaningful information for a tool with 25 parameters.

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

Completeness1/5

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

A tool with 25 optional filtering/sorting/pagination parameters and an output schema demands far more explanation than 'List catalogs'. Nothing about filtering operators, default page size, or the include expansion is addressed.

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

Parameters1/5

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

There are 25 parameters with only 8% schema description coverage, so the description must carry the burden of explaining sort/include/filter semantics. It explains none of them, leaving most parameters undocumented anywhere.

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

Purpose2/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

No indication of when to use this versus get_catalog, list_catalog_properties, or list_catalog_entities. An agent gets no routing guidance among the many catalog-related siblings.

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