Skip to main content
Glama
cuongtl1992

Unleash MCP (Feature Toggle)

getProjects

Retrieve a comprehensive list of all projects integrated with the Unleash Feature Toggle system for efficient project management and oversight.

Instructions

Get a list of all projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'getProjects' tool. It calls getAllProjects to fetch projects and formats the response as MCP content or an error.
    async function handleGetProjects() {
      try {
        const projects = await getAllProjects();
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(projects, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(
                {
                  success: false,
                  error: error.message,
                },
                null,
                2
              ),
            },
          ],
          isError: true,
        };
      }
    }
  • The tool definition object providing the name, description, and reference to the handler function. No input parameters schema is defined.
    export const getProjects = {
      name: 'getProjects',
      description: 'Get a list of all projects',
      handler: handleGetProjects,
    };
  • src/server.ts:171-175 (registration)
    Registration of the 'getProjects' tool on the MCP server instance using server.tool().
    server.tool(
      getProjects.name,
      getProjects.description,
      getProjects.handler as any
    );
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 'Get a list of all projects,' which implies a read-only operation, but doesn't specify details like pagination, sorting, filtering, error conditions, or response format. 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, efficient sentence with zero waste—'Get a list of all projects'—front-loading the core purpose without unnecessary details. It's appropriately sized for a simple retrieval tool, making it easy to parse and understand 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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it lacks context about what 'projects' entail, how the list is structured, or any limitations (e.g., access controls), making it incomplete for informed usage without additional assumptions or trial.

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%, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool, though it doesn't explicitly state 'no parameters required,' which could slightly improve clarity.

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 with a specific verb ('Get') and resource ('list of all projects'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'getProjectFeature' or 'getFeatureTypes', which also retrieve project-related data, so it doesn't fully distinguish its scope from alternatives.

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. With siblings like 'getProjectFeature' (likely for specific project features) and 'getFeatureTypes' (for feature metadata), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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

Related 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/cuongtl1992/unleash-mcp'

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