Skip to main content
Glama

studios_list

List all configured Pickaxe studios and identify the current default studio for managing AI agents, knowledge bases, and analytics.

Instructions

List all configured Pickaxe studios and the current default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'studios_list' tool. Retrieves configured studios using getConfiguredStudios(), determines default, and returns formatted JSON.
    case "studios_list": {
      const studios = getConfiguredStudios();
      const result = {
        studios,
        default: DEFAULT_STUDIO || (studios.length === 1 ? studios[0] : null),
        count: studios.length,
      };
      return JSON.stringify(result, null, 2);
    }
  • Tool schema definition for 'studios_list', including name, description, and empty input schema. Part of the tools list registered for ListToolsRequest.
    {
      name: "studios_list",
      description: "List all configured Pickaxe studios and the current default.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper function getConfiguredStudios() that scans environment variables for PICKAXE_STUDIO_* keys to list available studios. Used by the studios_list handler.
    function getConfiguredStudios(): string[] {
      const studios: string[] = [];
      for (const key of Object.keys(process.env)) {
        if (key.startsWith("PICKAXE_STUDIO_")) {
          const studioName = key.replace("PICKAXE_STUDIO_", "");
          studios.push(studioName);
        }
      }
      return studios;
    }
  • src/index.ts:616-618 (registration)
    Registration of all tools list handler, which returns the tools array containing 'studios_list' definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 it's a list operation, implying read-only behavior, but does not cover aspects like pagination, rate limits, authentication requirements, or error handling. This is a significant gap 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, well-structured sentence that is front-loaded with the main action ('List all configured Pickaxe studios') and adds a useful detail ('and the current default'). There is no wasted verbiage, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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), the description is adequate but has clear gaps. It explains what the tool does but lacks behavioral context (e.g., how results are formatted, any limitations). Without annotations or an output schema, the description should do more to compensate, but it meets the minimum viable threshold.

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 the schema description coverage is 100% (as there are no parameters to describe). The description does not need to add parameter details, so a baseline score of 4 is appropriate, as it efficiently avoids redundancy.

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

Purpose5/5

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

The description clearly states the specific action ('List all configured Pickaxe studios') and the resource ('studios'), and includes an additional output detail ('and the current default'). It distinguishes itself from sibling tools like 'doc_list' or 'user_list' by focusing specifically on studios.

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. It does not mention any prerequisites, exclusions, or comparisons to sibling tools, leaving the agent to infer usage based on the tool name 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

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/aplaceforallmystuff/mcp-pickaxe'

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