Skip to main content
Glama

env_project_list

List all projects that have specific environments assigned, helping manage API testing contexts.

Instructions

Lista todos los proyectos con entornos específicos asignados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'env_project_list'. It calls storage.listProjectEnvironments() and returns the list of project-to-environment mappings as JSON.
    'env_project_list',
    'Lista todos los proyectos con entornos específicos asignados.',
    {},
    async () => {
      try {
        const projectEnvs = await storage.listProjectEnvironments()
        const entries = Object.entries(projectEnvs)
    
        if (entries.length === 0) {
          return {
            content: [
              {
                type: 'text' as const,
                text: 'No hay entornos específicos por proyecto.',
              },
            ],
          }
        }
    
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(
                entries.map(([project, env]) => ({ project, environment: env })),
                null,
                2,
              ),
            },
          ],
        }
      } catch (error) {
        const message = error instanceof Error ? error.message : String(error)
        return {
          content: [{ type: 'text' as const, text: `Error: ${message}` }],
          isError: true,
        }
      }
    },
  • The storage helper method that lists project environments. Reads from project-envs.json file.
    async listProjectEnvironments(): Promise<Record<string, string>> {
      return this.getProjectEnvs()
    }
    
    private async getProjectEnvs(): Promise<Record<string, string>> {
      return (await this.readJson<Record<string, string>>(this.projectEnvsFile)) ?? {}
    }
  • The tool is registered via server.tool() with name 'env_project_list'. The registration is inside registerEnvironmentTools function.
    server.tool(
      'env_project_list',
  • The input schema is an empty object {} (no parameters required).
    {},
Behavior2/5

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

No annotations are present, so the description carries the full burden. It only states the purpose, without disclosing side effects (e.g., read-only), required permissions, or any behavioral traits. For a listing operation, it is acceptable but leaves the agent without safety guarantees.

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, front-loaded sentence that conveys the core purpose with no unnecessary words. It is concise and easy to parse.

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 output schema and no annotations, the description should provide more context. It does not define 'proyecto' or 'entornos específicos asignados', nor does it hint at the output format or typical usage. An agent may not know what to expect from the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the schema provides no constraints. The description adds minimal meaning beyond the name—it explains that the list is filtered to projects with 'specific environments assigned', but does not elaborate on what 'specific environments' means or how the results are structured. Baseline for 0 params is 4 but lack of detail justifies 3.

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 it lists projects ('Lista todos los proyectos') with a specific condition regarding environments. It is distinct from sibling tools like 'env_list' (lists environments) and 'env_project_clear' (clears assignments), but the phrase 'con entornos específicos asignados' is slightly ambiguous—it could mean projects that have environments assigned or projects with their assigned environments.

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. There is no mention of prerequisites, typical scenarios, or when not to use it. For example, it does not clarify whether this tool should be used before 'env_set' or 'env_project_clear'.

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/cocaxcode/api-testing-mcp'

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