Skip to main content
Glama

list_projects

Retrieve all API projects from Eolink OpenAPI to manage and integrate APIs within Windsurf IDE development workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'list_projects' tool, including inline schema (empty object, no params) and handler function that fetches projects and returns as JSON text.
      "list_projects",
      {}, // No parameters
      async () => {
        const projects = await this.getProjects();
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ projects }, null, 2) 
          }]
        };
      }
    );
  • Inline handler function for list_projects tool: calls this.getProjects() and formats projects as JSON text response.
    async () => {
      const projects = await this.getProjects();
      return {
        content: [{ 
          type: "text", 
          text: JSON.stringify({ projects }, null, 2) 
        }]
      };
    }
  • TypeScript interface Project defining the structure of project objects returned by list_projects.
    export interface Project {
      id: string;
      name: string;
      description?: string;
      createdAt: string;
      updatedAt: string;
    }
  • Helper method providing cached access to projects list, refreshing cache if empty.
    private async getProjects(): Promise<Project[]> {
      // Refresh projects if needed
      if (this.projects.length === 0) {
        await this.loadProjects();
      }
      return this.projects;
    }
  • Core helper that performs the HTTP request to Eolink API endpoint /projects to fetch the list of projects.
    async getProjects(): Promise<Project[]> {
      try {
        const response = await axios.get(`${this.baseUrl}/projects`, {
          headers: this.getHeaders(),
        });
        return response.data.data || [];
      } catch (error) {
        console.error('Error fetching projects:', error);
        return [];
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/scarqin/mcp-apikit'

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