Skip to main content
Glama
fkom13

MCP SFTP Orchestrator

by fkom13

Lister les APIs du catalogue

api_list

List all configured APIs in the MCP SFTP Orchestrator catalogue to monitor API health and manage remote server connections.

Instructions

Affiche toutes les APIs configurées dans le catalogue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:149-160 (registration)
    Full registration of the 'api_list' MCP tool, including schema (empty input), description, and handler that delegates to apis.listApis() and formats as JSON response.
    server.registerTool(
        "api_list",
        {
            title: "Lister les APIs du catalogue",
            description: "Affiche toutes les APIs configurées dans le catalogue.",
            inputSchema: z.object({})
        },
        async () => {
            const apiList = await apis.listApis();
            return { content: [{ type: "text", text: JSON.stringify(apiList, null, 2) }] };
        }
    );
  • apis.js:70-74 (helper)
    Core implementation of listApis(): ensures APIs are loaded/initialized and returns the apis object containing all configured APIs.
    // Lister toutes les APIs
    async function listApis() {
        await ensureInitialized();
        return apis;
    }
Behavior2/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 of behavioral disclosure. It states the tool displays all APIs, implying a read-only operation, but doesn't specify details like whether it requires authentication, how data is formatted (e.g., pagination, sorting), or potential rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is a single, clear sentence: 'Affiche toutes les APIs configurées dans le catalogue.' It's front-loaded with the core purpose, has no unnecessary words, and efficiently conveys the essential information without waste.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It states what the tool does but lacks context about usage, behavior, or output format. For a basic list tool, it meets the minimum viable standard but could be more helpful by adding details like output structure or when to use it.

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 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, as there are none. A baseline score of 4 is appropriate for tools with no parameters, as there's nothing to compensate for.

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 tool's purpose: 'Affiche toutes les APIs configurées dans le catalogue' (Displays all APIs configured in the catalog). It specifies the verb 'affiche' (displays) and the resource 'APIs du catalogue' (APIs in the catalog). However, it doesn't explicitly differentiate from sibling tools like 'server_list' or 'task_history', which also list resources but different types.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparisons to siblings like 'api_check' or 'api_add'. There's no indication of when this tool is appropriate or when other tools might be better suited.

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/fkom13/mcp-sftp-orchestrator'

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