Core Content Services MCP Server

Official

by ibm-ecm

Overview Schema Source Related Servers Discussions Admin

Python

Remote

repository_object_search

Search for non-document repository objects by class and property filters. Returns object details with properties.

Instructions

PREREQUISITES IN ORDER: To use this tool, you MUST call two other tools first in a specific sequence.

determine_class tool to get the class_name for search_class.
get_searchable_property_descriptions to get a list of valid property_name for search_properties

Description: This tool retrieves repository objects other than Document instances.

:param search_parameters (SearchParameters): parameters for the searching including the object being searched for and any search conditions.

:returns: A the repository object details, including: - repositoryObjects (dict): a dictionary containing independentObjects: - independentObjects (list): A list of independent objects, each containing: - properties (list): A list of properties, each containing: - label (str): The name of the property. - value (str): The value of the property.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`search_parameters`	Yes	Complete set of parameters for executing a repository search.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.0.4May 4, 2026

removedInput schema / $defs

Removed value: -{
-  "SearchOperator": {
-    "description": "Enum defining all valid search operators for repository searches.\n\nThese operators determine how property values are compared during searches.",
-    "enum": [
-      "=",
-      ">",
-      "<",
-      ">=",
-      "<=",
-      "!=",
-      "CONTAINS",
-      "STARTS",
-      "ENDS"
-    ],
-    "title": "SearchOperator",
-    "type": "string"
-  },
-  "SearchParameters": {
-    "description": "Complete set of parameters for executing a repository search.",
-    "properties": {
-      "search_class": {
-        "description": "The class to search for. Must be a valid class in the repository.",
-        "title": "Search Class",
-        "type": "string"
-      },
-      "search_properties": {
-        "description": "List of filter conditions to apply to the search. All conditions are combined with AND logic. If no conditions exist, we return all objects of the given class",
-        "items": {
-          "$ref": "#/$defs/SearchProperty"
-        },
-        "title": "Search Properties",
-        "type": "array"
-      }
-    },
-    "required": [
-      "search_class",
-      "search_properties"
-    ],
-    "title": "SearchParameters",
-    "type": "object"
-  },
-  "SearchProperty": {
-    "description": "Defines a single search condition/filter to be applied during repository searches.",
-    "properties": {
-      "operator": {
-        "$ref": "#/$defs/SearchOperator",
-        "description": "The comparison operator that defines how property_name and property_value are compared. Use CONTAINS for substring matching, STARTS/ENDS for prefix/suffix matching. Use standard SQL operators: =, >, <, >=, <=, != for other properties."
-      },
-      "property_name": {
-        "description": "The name of the property to filter on. Must be a valid property for the specified class as obtained from the get_searchable_class_properties_tool .",
-        "title": "Property Name",
-        "type": "string"
-      },
-      "property_value": {
-        "description": "The value to filter by. Format should match the property's data type.",
-        "title": "Property Value",
-        "type": "string"
-      }
-    },
-    "required": [
-      "property_name",
-      "property_value",
-      "operator"
-    ],
-    "title": "SearchProperty",
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / search_parameters / $ref
```
Removed value: -"#/$defs/SearchParameters"
```

addedInput schema / properties / search_parameters / description

Added value: +"Complete set of parameters for executing a repository search."

addedInput schema / properties / search_parameters / properties

Added value: +{
+  "search_class": {
+    "description": "The class to search for. Must be a valid class in the repository.",
+    "type": "string"
+  },
+  "search_properties": {
+    "description": "List of filter conditions to apply to the search. All conditions are combined with AND logic. If no conditions exist, we return all objects of the given class",
+    "items": {
+      "description": "Defines a single search condition/filter to be applied during repository searches.",
+      "properties": {
+        "operator": {
+          "description": "The comparison operator that defines how property_name and property_value are compared. Use CONTAINS for substring matching, STARTS/ENDS for prefix/suffix matching. Use standard SQL operators: =, >, <, >=, <=, != for other properties.",
+          "enum": [
+            "=",
+            ">",
+            "<",
+            ">=",
+            "<=",
+            "!=",
+            "CONTAINS",
+            "STARTS",
+            "ENDS"
+          ],
+          "type": "string"
+        },
+        "property_name": {
+          "description": "The name of the property to filter on. Must be a valid property for the specified class as obtained from the get_searchable_class_properties_tool .",
+          "type": "string"
+        },
+        "property_value": {
+          "description": "The value to filter by. Format should match the property's data type.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "property_name",
+        "property_value",
+        "operator"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / search_parameters / required

Added value: +[
+  "search_class",
+  "search_properties"
+]

addedInput schema / properties / search_parameters / type
```
Added value: +"object"
```

removedInput schema / title

Removed value: -"get_repository_object_mainArguments"

removedOutput schema / $defs

Removed value: -{
-  "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: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/ToolError"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "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: -"get_repository_object_mainOutput"

addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

First observedv1.0.0Jan 8, 2026

TDQS

A4/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 implies a read-only operation ('retrieves') but does not explicitly state safety or side effects; however, it does describe return structure in detail.

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

Conciseness3/5

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

The description is verbose with a prerequisite block and param docs that repeat schema; while the prerequisite info is valuable, the structure could be more concise and front-loaded.

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's complexity (nested params, no annotations), the description covers prerequisites and return structure, making it mostly complete. Missing details on pagination or error handling keep it from a 5.

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 coverage is 100%, and the description's param docs largely mirror the schema. The description adds no new meaning beyond the schema, so baseline 3 is appropriate.

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 it 'retrieves repository objects other than Document instances,' which is specific verb+resource and distinguishes it from the sibling tool 'document_search'.

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 lists prerequisites in order (determine_class then get_searchable_property_descriptions) and implies this tool is for non-document objects, providing clear when-to-use and when-not-to-use guidance.

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