Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ce_get_project

Retrieve details of an IBM Cloud Code Engine project by providing its ID and region.

Instructions

Get Code Engine project details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
regionNo

Implementation Reference

  • The handler for 'ce_get_project' - performs an HTTP GET request to the Code Engine API at /projects/{project_id} using the client, wrapped in safeTool for error handling.
    server.tool("ce_get_project", "Get Code Engine project details", {
      project_id: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(() => client.get(`${base(p.region||r)}/projects/${p.project_id}`)));
  • Input schema for 'ce_get_project' - requires 'project_id' (string) and optional 'region' (string), validated by Zod.
    server.tool("ce_get_project", "Get Code Engine project details", {
      project_id: z.string(), region: z.string().optional(),
  • Registration of 'ce_get_project' tool via server.tool('ce_get_project', ...) in the registerCodeEngineTools function.
    server.tool("ce_get_project", "Get Code Engine project details", {
  • src/server.ts:62-62 (registration)
    Call to registerCodeEngineTools(server, client, config) which registers all Code Engine tools including 'ce_get_project'.
    registerCodeEngineTools(server, client, config);
  • The CODE_ENGINE endpoint builder function used to construct the API URL for the 'ce_get_project' request.
    CODE_ENGINE: (region: string) =>
      `https://api.${region}.codeengine.cloud.ibm.com/v2`,
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the action without mentioning permissions, rate limits, or what 'details' include.

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 very short but still clear and front-loaded, though it lacks helpful detail without becoming verbose.

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 lack of output schema and annotations, the description fails to explain what the tool returns or provide enough context for reliable use.

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?

Schema coverage is 0% and the description adds no meaning to the parameters 'project_id' and 'region', leaving the agent uninformed about their expected values.

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 gets details of a Code Engine project, distinguishing it from sibling tools like ce_create_project or ce_delete_project.

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?

No guidance on when to use this tool versus alternatives, nor any context about prerequisites or side effects.

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