Core Content Services MCP Server

Official

by ibm-ecm

Overview Schema Source Related Servers Discussions Admin

Python

Remote

determine_class

Find classes matching keywords by searching within a specified root class. Returns up to 3 matches with scores.

Instructions

Find classes that match the given keywords by looking for substring matches in class names and descriptions.

IMPORTANT: To get a list of all valid class names that can be used with this tool, you MUST first call the list_root_classes_tool tool.

:param root_class: The root class to search within (eg. "Document", "Folder") :param keywords: Up to 3 words from the user's message that might contain the class's name

:returns: A list of up to 3 matching classes with their scores, or a ToolError if no matches are found Each match is a ClassMatch object with class_name and score fields

Input Schema

TableJSON Schema

Name	Required	Description	Default
`root_class`	Yes
`keywords`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.0.4May 4, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / keywords / title
```
Removed value: -"Keywords"
```
removedInput schema / properties / root_class / title
```
Removed value: -"Root Class"
```

removedInput schema / title

Removed value: -"determine_classArguments"

removedOutput schema / $defs

Removed value: -{
-  "ClassDescriptionData": {
-    "description": "Information about a class in the content repository.",
-    "properties": {
-      "descriptive_text": {
-        "description": "Describes additional details about this class",
-        "title": "Descriptive Text",
-        "type": "string"
-      },
-      "display_name": {
-        "description": "The display name of the class",
-        "title": "Display Name",
-        "type": "string"
-      },
-      "symbolic_name": {
-        "description": "Symbolic name that is used to reference this class",
-        "title": "Symbolic Name",
-        "type": "string"
-      }
-    },
-    "required": [
-      "display_name",
-      "symbolic_name",
-      "descriptive_text"
-    ],
-    "title": "ClassDescriptionData",
-    "type": "object"
-  },
-  "ClassMatch": {
-    "description": "Represents a matched class with its score and additional information.\n\nThis class contains information about a class that matched a search query,\nincluding its class description data and match score.\nThe score indicates how well the class matched the search criteria,\nwith higher values representing better matches.",
-    "properties": {
-      "class_description_data": {
-        "$ref": "#/$defs/ClassDescriptionData",
-        "description": "The complete class description data object containing class_name, display_name, and descriptive_text"
-      },
-      "score": {
-        "description": "The match score, higher values indicate better matches",
-        "title": "Score",
-        "type": "number"
-      }
-    },
-    "required": [
-      "class_description_data",
-      "score"
-    ],
-    "title": "ClassMatch",
-    "type": "object"
-  },
-  "ToolError": {
-    "description": "Represents an error response from a tool execution.\n\nThis class helps the LLM understand error messages and provides suggestions\nfor potential resolutions.",
-    "properties": {
-      "isError": {
-        "const": true,
-        "default": true,
-        "description": "Indicates that an error occurred during tool execution if value is True",
-        "title": "Iserror",
-        "type": "boolean"
-      },
-      "message": {
-        "description": "Detailed error message",
-        "title": "Message",
-        "type": "string"
-      },
-      "suggestions": {
-        "description": "List of suggestions for resolving the error",
-        "items": {
-          "type": "string"
-        },
-        "title": "Suggestions",
-        "type": "array"
-      }
-    },
-    "required": [
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/ClassMatch"
-    },
-    "type": "array"
-  },
-  {
-    "$ref": "#/$defs/ToolError"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Represents a matched class with its score and additional information.\n\nThis class contains information about a class that matched a search query,\nincluding its class description data and match score.\nThe score indicates how well the class matched the search criteria,\nwith higher values representing better matches.",
+      "properties": {
+        "class_description_data": {
+          "description": "The complete class description data object containing class_name, display_name, and descriptive_text",
+          "properties": {
+            "descriptive_text": {
+              "description": "Describes additional details about this class",
+              "type": "string"
+            },
+            "display_name": {
+              "description": "The display name of the class",
+              "type": "string"
+            },
+            "symbolic_name": {
+              "description": "Symbolic name that is used to reference this class",
+              "type": "string"
+            }
+          },
+          "required": [
+            "display_name",
+            "symbolic_name",
+            "descriptive_text"
+          ],
+          "type": "object"
+        },
+        "score": {
+          "description": "The match score, higher values indicate better matches",
+          "type": "number"
+        }
+      },
+      "required": [
+        "class_description_data",
+        "score"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "description": "Represents an error response from a tool execution.\n\nThis class helps the LLM understand error messages and provides suggestions\nfor potential resolutions.",
+    "properties": {
+      "isError": {
+        "const": true,
+        "default": true,
+        "description": "Indicates that an error occurred during tool execution if value is True",
+        "type": "boolean"
+      },
+      "message": {
+        "description": "Detailed error message",
+        "type": "string"
+      },
+      "suggestions": {
+        "description": "List of suggestions for resolving the error",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "message"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"determine_classOutput"
```
addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

First observedv1.0.0Jan 8, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations exist, so the description must disclose behavior. It explains substring matching, return of up to 3 classes with scores, and error on no matches. However, it omits details like case sensitivity or score meaning, leaving some gap.

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?

Description is concise with a clear first sentence, structured :param/:returns format, and no redundant text. Each sentence adds value.

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

Completeness5/5

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

Given the output schema existence and tool complexity, the description covers search method, parameters, return format, and prerequisite, making it fully adequate for agent use.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates by explaining root_class and keywords with examples and constraints (e.g., 'up to 3 words'), adding meaning beyond type definitions.

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 explicitly states the tool finds classes by substring matching in names and descriptions, clearly distinguishing it from siblings like list_root_classes or get_class_property_descriptions.

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 explicit prerequisite: 'MUST first call list_root_classes_tool' for valid class names, and gives parameter constraints (up to 3 keywords) and examples (root_class like 'Document').

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