Skip to main content
Glama
ibm-ecm

IBM Core Content Services MCP Server

Official
by ibm-ecm
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_root_classes

Retrieve all root class types in IBM Content Manager to identify valid class names before listing all classes.

Instructions

List all available root class types in the repository.

This tool should be called first to get a list of valid root class names before using the list_all_classes tool.

:returns: A list of all available root class types (e.g., ["Document", "Folder", "Annotation", "CustomObject"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/cs_mcp_server/tools/classes.py:466-475 (handler)
    The handler function that executes the tool logic. It simply returns the root class keys from the metadata cache.
    def list_root_classes_tool() -> List[str]:
    """
    List all available root class types in the repository.

    This tool should be called first to get a list of valid root class names
    before using the list_all_classes tool.

    :returns: A list of all available root class types (e.g., ["Document", "Folder", "Annotation", "CustomObject"])
    """
    return metadata_cache.get_root_class_keys()
  • src/cs_mcp_server/tools/classes.py:463-465 (registration)
    The @mcp.tool decorator that registers the list_root_classes tool with the MCP server.
    @mcp.tool(
    name="list_root_classes",
)
  • src/cs_mcp_server/mcp_server_main.py:222-222 (registration)
    Call to register_class_tools which defines and registers the class tools including list_root_classes for CORE server type.
    register_class_tools(mcp, graphql_client, metadata_cache)
  • src/cs_mcp_server/mcp_server_main.py:238-238 (registration)
    Call to register_class_tools which defines and registers the class tools including list_root_classes for FULL server type.
    register_class_tools(mcp, graphql_client, metadata_cache)

Tool Definition Quality

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates this is a read operation (listing) and mentions the return format, but doesn't cover other behavioral aspects like error conditions, authentication needs, or rate limits. For a zero-parameter tool, this is minimally adequate but lacks depth.

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 front-loaded with the core purpose, followed by usage guidance and return details. Every sentence adds value without redundancy, making it efficient and well-structured for quick comprehension.

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?

Given the tool has 0 parameters, an output schema exists (so return values are documented elsewhere), and it's a simple read operation, the description covers purpose and usage well. However, without annotations, it could benefit from more behavioral context like error handling, but for this complexity level, it's largely complete.

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?

The tool has 0 parameters with 100% schema coverage, so the baseline is 4. The description doesn't need to explain parameters, and it appropriately focuses on the tool's purpose and output instead.

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 specific action ('List all available root class types') and resource ('in the repository'), distinguishing it from siblings like 'list_all_classes' which appears to be a different scope. It uses precise terminology that indicates its role in the system.

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 explicitly states when to use this tool ('should be called first to get a list of valid root class names before using the list_all_classes tool'), providing clear sequencing guidance and naming the alternative tool. This gives the agent direct operational context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibm-ecm/ibm-content-services-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server