Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

schematics_get_workspace

Retrieve details of a specific IBM Cloud Schematics workspace by providing the workspace ID.

Instructions

Get workspace details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYes

Implementation Reference

  • The actual handler for schematics_get_workspace. It registers an MCP tool that takes a workspace_id parameter (z.string()) and performs a GET request to the Schematics v1 API endpoint `${base}/workspaces/${p.workspace_id}` using the IBMCloudAPIClient, wrapped in safeTool for error handling.
    server.tool("schematics_get_workspace", "Get workspace details", {
      workspace_id: z.string(),
    }, async (p) => safeTool(() => client.get(`${base}/workspaces/${p.workspace_id}`)));
  • The input schema for schematics_get_workspace: requires a single string parameter 'workspace_id' validated via Zod (z.string()).
    server.tool("schematics_get_workspace", "Get workspace details", {
      workspace_id: z.string(),
    }, async (p) => safeTool(() => client.get(`${base}/workspaces/${p.workspace_id}`)));
  • src/server.ts:83-84 (registration)
    The tool is registered at the server level by calling registerSchematicsTools(server, client, config) inside createServer(), which is where all tool sets are wired together.
    registerSchematicsTools(server, client, config);
    console.error(`  ✓ Schematics (8 tools)`);
  • The SCHEMATICS endpoint definition used to build the base URL: `https://schematics.{region}.cloud.ibm.com/v1` for v1 API calls, and `https://schematics.{region}.cloud.ibm.com/v2` for v2.
    SCHEMATICS: (region: string) =>
      `https://schematics.${region}.cloud.ibm.com/v1`,
    SCHEMATICS_V2: (region: string) =>
      `https://schematics.${region}.cloud.ibm.com/v2`,
  • The get() method on IBMCloudAPIClient that executes the actual HTTP GET request. It delegates to the generic request() method with method: 'GET'.
    async get<T = unknown>(url: string, queryParams?: Record<string, string | number | boolean | undefined>): Promise<T> {
      return this.request<T>(url, { method: "GET", queryParams });
    }
Behavior2/5

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

No annotations are present, so the description carries the full burden. 'Get' implies a read-only operation, but no behavioral traits (e.g., idempotency, required permissions, error conditions) are disclosed. The description adds minimal value beyond the name.

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?

The description is only three words, which is excessively terse. While it avoids verbosity, it omits critical information, making it underspecified rather than appropriately concise.

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

Completeness2/5

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

Given the tool has one parameter and no output schema, the description should provide context about return values, potential errors, or workspace identification. It does none of these, leaving the agent underinformed for correct invocation.

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?

The schema has 0% description coverage for the single parameter workspace_id. The description adds no meaning or context for this parameter, such as how to obtain it or its format. With no parameter documentation, the description fails to compensate.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'workspace details', making the tool's purpose obvious. It distinguishes itself from sibling schematics_list_workspaces (which lists all workspaces) and schematics_get_job (gets a job). However, it doesn't specify the scope or content of 'details', which could be more precise.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like schematics_list_workspaces or schematics_get_job. No usage context, prerequisites, or exclusions are provided.

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/ahmedselimmansor-ctrl/IBM_cloud_MCP_SERVER'

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