Skip to main content
Glama
filipecalegario

strateegia MCP Server

list-projects

Retrieve and display all available projects from the Strateegia platform for project management and collaboration.

Instructions

List projects from Strateegia API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list-projects' tool. Fetches project data from Strateegia API, processes labs and projects, and returns a formatted text response.
    if (request.params.name === "list-projects") {
        const labs: StrateegiaItemResponse[] = await fetchStrateegiaAPI(
            "/projects/v1/project"
        );
    
        if (labs.length === 0) {
            return {
                content: [
                    {
                        type: "text",
                        text: "No labs found. Make sure your access token has the correct permissions.",
                    },
                ],
            };
        }
    
        let labCount = 0;
        let projectCount = 0;
    
        const projectsSummary = labs
            .map((item) => {
                labCount++;
                projectCount += item.projects.length;
                return `Lab: ${item.lab.name} (ID: ${
                    item.lab.id
                })\nProjects:\n${item.projects
                    .map((project) => {
                        return `- ${project.title} (ID: ${project.id})`;
                    })
                    .join("\n")}`;
            })
            .join("\n\n");
    
        const fullResponse = `Found ${labCount} labs and ${projectCount} projects:\n\n${projectsSummary}`;
    
        return {
            content: [
                {
                    type: "text",
                    text: fullResponse,
                },
            ],
        };
    }
  • Tool definition including name, description, and input schema (empty object, no parameters required).
    const LIST_PROJECTS_TOOL: Tool = {
        name: "list-projects",
        description: "List projects from Strateegia API",
        inputSchema: {
            type: "object",
            properties: {},
            required: [],
        },
    };
  • src/index.ts:106-108 (registration)
    Registers the 'list-projects' tool in the ListToolsRequest handler so it appears in tool lists.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: [LIST_PROJECTS_TOOL],
    }));
  • Helper function to perform authenticated fetches to the Strateegia API, called by the list-projects handler.
    async function fetchStrateegiaAPI(endpoint: string): Promise<any> {
        const accessToken = await getAccessToken();
        const response = await fetch(`${API_BASE_URL}${endpoint}`, {
            headers: {
                Authorization: `Bearer ${accessToken}`,
                "Content-Type": "application/json",
            },
        });
    
        if (!response.ok) {
            const errorText = await response.text();
            throw new Error(
                `API request failed: ${response.status} ${response.statusText} - ${errorText}`
            );
        }
    
        return response.json();
    }
  • Helper function to obtain an access token using the STRATEEGIA_API_KEY environment variable, used by fetchStrateegiaAPI.
    async function getAccessToken(): Promise<string> {
        const api_key = process.env.STRATEEGIA_API_KEY;
        if (!api_key) {
            throw new Error("STRATEEGIA_API_KEY environment variable is not set");
        }
    
        const options = {
            method: "POST",
            headers: {
                "x-api-key": api_key,
            },
        };
    
        async function fetchAccessToken() {
            const response = await fetch(API_AUTH_BASE, options);
            if (!response.ok) {
                const errorText = await response.text();
                throw new Error(
                    `API request failed: ${response.status} ${response.statusText} - ${errorText}`
                );
            }
            return response.json();
        }
    
        const token = await fetchAccessToken();
        return token.access_token;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states what the tool does ('List projects'), without disclosing behavioral traits like pagination, rate limits, authentication needs, or response format. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence with no wasted words, front-loading the core action. It's appropriately sized for a simple list tool, making it easy for an agent to parse quickly.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavior, response format, or any context needed for effective use. For a tool with such minimal structured data, the description should provide more operational insight.

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 with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't need to add parameter details, and it appropriately doesn't mention any. Baseline is 4 for zero parameters, as no compensation is needed.

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 action ('List') and resource ('projects from Strateegia API'), making the purpose understandable. It lacks sibling tools for differentiation, but the verb+resource combination is specific enough for a standalone tool. No tautology or misleading elements are present.

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, such as context, prerequisites, or alternatives. With no siblings mentioned, it doesn't need to differentiate, but it fails to offer any usage context, leaving the agent without direction on appropriate scenarios.

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/filipecalegario/mcp-server-strateegia'

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