Skip to main content
Glama

project_instances_status

Check the current operational status of all active project instances to monitor progress and identify issues requiring attention.

Instructions

Get status of all active project instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and inline handler for the 'project_instances_status' MCP tool. Calls projectManager.getInstancesStatus() and formats the output as a status report.
    server.tool(
      "project_instances_status",
      "Get status of all active project instances",
      {},
      async () => {
        try {
          const status = projectManager.getInstancesStatus();
          const instanceCount = Object.keys(status).length;
          
          if (instanceCount === 0) {
            return {
              content: [
                {
                  type: "text", 
                  text: `šŸ“Š **Status Istanze Progetto**\n\nāŒ Nessuna istanza attiva.`
                }
              ]
            };
          }
    
          let statusText = `šŸ“Š **Status Istanze Progetto** (${instanceCount} attive)\n\n`;
          
          for (const [projectId, info] of Object.entries(status)) {
            const uptime = Math.floor((info.uptime || 0) / 1000);
            const lastUsed = info.lastUsed ? Math.floor((Date.now() - info.lastUsed) / 1000) : 'Mai';
            
            statusText += `šŸ”§ **${info.name}**\n`;
            statusText += `   • ID: ${projectId}\n`;
            statusText += `   • Status: ${info.isActive ? 'āœ… Attiva' : 'āŒ Inattiva'}\n`;
            statusText += `   • Uptime: ${uptime}s\n`;
            statusText += `   • Ultimo uso: ${lastUsed}s fa\n`;
            statusText += `   • Network: ${info.stats?.nodes} nodi, ${info.stats?.links} link\n\n`;
          }
          
          return {
            content: [
              {
                type: "text",
                text: statusText
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `āŒ **Errore:** ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Core helper method implementing getInstancesStatus() in ProjectInstanceManager class. Iterates over active project instances and returns their status objects with uptime and stats.
    public getInstancesStatus(): { [projectId: string]: any } {
      const status: { [projectId: string]: any } = {};
      
      for (const [projectId, instance] of this.projectInstances) {
        status[projectId] = {
          name: instance.config.name,
          description: instance.config.description,
          isActive: instance.isActive,
          startTime: instance.startTime,
          lastUsed: instance.lastUsed,
          uptime: instance.startTime ? Date.now() - instance.startTime : 0,
          stats: instance.stats
        };
      }
      
      return status;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get status'), but doesn't specify details like whether it requires authentication, how it handles errors, what the return format is, or if there are rate limits. 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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and wastes no space, 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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'status' entails (e.g., what data is returned), how 'active' is defined, or any behavioral traits like error handling. For a tool with no structured data to rely on, this leaves too many gaps for effective agent use.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately doesn't discuss parameters, and since there are none, it doesn't need to compensate for any gaps. This meets the baseline for tools with no parameters.

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 ('Get status') and target resource ('all active project instances'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'project_status' or 'project_health_check', which might have overlapping functionality, so it doesn't reach the highest score.

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 like 'project_status' or 'project_health_check' from the sibling list. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on the 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/multiluca2020/visum-thinker-mcp-server'

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