Skip to main content
Glama

env_group_remove_scope

Remove a directory scope from an environment group in API Testing MCP. Specify the group name and optionally the directory path to remove the current directory.

Instructions

Quita un directorio (scope) de un grupo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesNombre del grupo
scopeNoRuta del directorio a quitar. Si se omite, usa el directorio actual

Implementation Reference

  • Handler for env_group_remove_scope tool. Takes 'group' and optional 'scope' (defaults to CWD) params, calls storage.removeScopeFromGroup to remove the scope from the group.
    async (params) => {
      try {
        const scope = params.scope ?? process.cwd()
        await storage.removeScopeFromGroup(params.group, scope)
        return {
          content: [{ type: 'text' as const, text: `Scope '${scope}' eliminado del grupo '${params.group}'` }],
        }
      } catch (error) {
        const message = error instanceof Error ? error.message : String(error)
        return { content: [{ type: 'text' as const, text: `Error: ${message}` }], isError: true }
      }
    },
  • Schema/input definition for env_group_remove_scope: 'group' (required string) and 'scope' (optional string, defaults to current directory).
    'Quita un directorio (scope) de un grupo.',
    {
      group: z.string().describe('Nombre del grupo'),
      scope: z.string().optional().describe('Ruta del directorio a quitar. Si se omite, usa el directorio actual'),
  • Registration of the 'env_group_remove_scope' tool on the MCP server using server.tool().
    server.tool(
      'env_group_remove_scope',
      'Quita un directorio (scope) de un grupo.',
      {
        group: z.string().describe('Nombre del grupo'),
        scope: z.string().optional().describe('Ruta del directorio a quitar. Si se omite, usa el directorio actual'),
      },
      async (params) => {
        try {
          const scope = params.scope ?? process.cwd()
          await storage.removeScopeFromGroup(params.group, scope)
          return {
            content: [{ type: 'text' as const, text: `Scope '${scope}' eliminado del grupo '${params.group}'` }],
          }
        } catch (error) {
          const message = error instanceof Error ? error.message : String(error)
          return { content: [{ type: 'text' as const, text: `Error: ${message}` }], isError: true }
        }
      },
    )
  • Storage helper that removes a scope from a group by normalizing path, filtering it from group.scopes, updating timestamp, and saving.
    async removeScopeFromGroup(groupName: string, scope: string): Promise<void> {
      const group = await this.getGroup(groupName)
      if (!group) {
        throw new Error(`Grupo '${groupName}' no encontrado`)
      }
      const normalized = scope.replace(/\\/g, '/')
      group.scopes = group.scopes.filter((s) => s !== normalized)
      group.updatedAt = new Date().toISOString()
      await this.saveGroup(group)
    }
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It implies a destructive action (removing a scope) but does not disclose side effects, permissions needed, or whether changes are reversible. The description is minimal and insufficient for an agent to fully understand the impact.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded with the core action. It wastes no words, but its brevity may sacrifice completeness. Still, it earns a 4 for efficiency.

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 simplicity of the tool (two parameters, no output schema, no annotations) and the presence of sibling tools (env_group_add_scope, env_group_create, etc.), the description is incomplete. It lacks information on error cases, group existence requirements, and differentiation from similar operations. An agent cannot reliably decide when to invoke this tool based solely on the description.

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?

Schema coverage is 100%, so the input schema already provides descriptions for both parameters (group name, scope path with default behavior). The tool description adds no additional semantic value beyond restating the action. Baseline of 3 is appropriate.

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 function: removing a scope (directory) from a group. The verb 'quitar' (remove) and resource 'directorio (scope) de un grupo' are specific. However, it does not explicitly differentiate from sibling tools like env_group_add_scope, which is the inverse operation.

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, such as env_group_add_scope or env_group_delete. There is no mention of prerequisites, context, or when removal is appropriate.

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