Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

cf_list_routes

List all Cloud Foundry routes in a given space. Provide a space GUID to retrieve routes for that space.

Instructions

List Cloud Foundry routes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_guidNo

Implementation Reference

  • The handler for cf_list_routes. Makes a GET request to the CF v3/routes API endpoint with an optional space_guid filter.
    server.tool("cf_list_routes", "List Cloud Foundry routes", {
      space_guid: z.string().optional(),
    }, async (p) => safeTool(() => client.get(`${base}/v3/routes`, {space_guids:p.space_guid})));
  • Input schema for cf_list_routes: accepts an optional space_guid string parameter.
    space_guid: z.string().optional(),
  • Registration of the cf_list_routes tool on the MCP server via server.tool().
    server.tool("cf_list_routes", "List Cloud Foundry routes", {
      space_guid: z.string().optional(),
    }, async (p) => safeTool(() => client.get(`${base}/v3/routes`, {space_guids:p.space_guid})));
  • src/server.ts:89-90 (registration)
    The Cloud Foundry tool registration is invoked in createServer() which registers all Cloud Foundry tools including cf_list_routes.
    registerCloudFoundryTools(server, client, config);
    console.error(`  ✓ Cloud Foundry (6 tools)`);
  • The base URL constant for Cloud Foundry API, used as the endpoint for cf_list_routes requests.
    CLOUD_FOUNDRY: "https://api.us-south.cf.cloud.ibm.com",
Behavior2/5

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

The description only says 'List' which implies read-only, but no annotations are provided to confirm. There is no disclosure about pagination, rate limits, error handling, or the behavior of the optional space_guid parameter.

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 extremely concise but at the cost of informativeness. It is a single phrase that provides no additional context, making it under-specified for effective tool selection.

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

Completeness1/5

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

Given no output schema and minimal description, the tool lacks crucial information such as return format, pagination, and parameter details. It fails to provide a complete picture for the agent.

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 input schema has one parameter (space_guid) with 0% description coverage, and the description does not mention it or explain its purpose. The description adds no value beyond what the schema provides.

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 'List Cloud Foundry routes' clearly states the action (list) and resource (routes). However, it does not distinguish from the sibling tool 'at_list_routes', which likely has similar functionality.

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 is provided on when to use this tool versus alternatives (e.g., at_list_routes, cf_list_apps). There is no mention of prerequisites, scope, or typical use cases.

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