Skip to main content
Glama
matlock08

Watson Discovery MCP Server

by matlock08

get_projects

Retrieve a list of Watson Discovery projects with names, UUIDs, and types for inventory or selection in subsequent operations.

Instructions

Watson Discovery Get Projects

Description

The Watson Discovery Get Projects tool provides access to IBM Watson Discovery's projects, allowing you to retrieve a list of all available projects in your Watson Discovery instance. This tool returns both the human-readable project names and their corresponding unique identifiers (UUIDs) for use in subsequent operations.

Function

This tool connects to your IBM Watson Discovery instance using your provided authentication credentials, queries the available projects, and returns structured information about each project.

Use Cases

  • Inventory management of Watson Discovery projects

  • Project selection for further operations, such as querying or collection management

  • Pre-processing step before performing operations on specific projects

  • Integration with automated workflows that require project UUIDs

Authentication

This tool requires valid IBM Cloud IAM API credentials to access your Watson Discovery instance. Ensure your service account has appropriate permissions to list projects.

Output Format

Results are returned as a structured array of project objects, each containing:

  • name: The project name (string)

  • project_id: The project's UUID (string in UUID format)

  • type: The type of project Possible values: [intelligent_document_processing,document_retrieval,conversational_search,content_mining,content_intelligence,other] (string)

  • collection_count: The number of collections configured in this project (integer)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Without annotations, the description covers behavioral aspects like authentication needs and output structure. It explicitly states the function is to list projects, implying no destructive side effects, though it could state 'read-only' more directly.

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?

The description is well-structured with sections and front-loaded main purpose. It is slightly verbose but every section contributes useful context without excessive repetition.

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 no output schema, the description fully explains the return structure (name, project_id, type, collection_count) and authentication. It is complete for a list operation with no parameters.

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 zero parameters and 100% schema coverage, so description adds value beyond schema by detailing output fields and authentication. Baseline of 4 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 a list of projects with human-readable names and UUIDs. It distinguishes from sibling tools like 'list_project_collections' and 'query_project' by focusing exclusively on projects.

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

Usage Guidelines4/5

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

The description lists concrete use cases and mentions authentication requirements, implying when to use it (e.g., inventory, pre-processing). It doesn't explicitly contrast with alternatives, but the sibling tools are sufficiently different to avoid confusion.

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/matlock08/watson_discovery_mcp'

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