Skip to main content
Glama

twining_agents

View all active agents with their capabilities and status to coordinate development tasks through a shared blackboard and knowledge graph.

Instructions

List all registered agents with their capabilities and liveness status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_goneNoWhether to include gone agents (default: true)

Implementation Reference

  • The handler for the 'twining_agents' tool, which fetches all registered agents and computes their liveness status.
    async (args) => {
      try {
        const includeGone = args.include_gone ?? true;
        const agents = await agentStore.getAll();
        const thresholds =
          config.agents?.liveness ?? DEFAULT_LIVENESS_THRESHOLDS;
        const now = new Date();
    
        const mapped = agents.map((agent) => ({
          agent_id: agent.agent_id,
          capabilities: agent.capabilities,
          role: agent.role,
          description: agent.description,
          registered_at: agent.registered_at,
          last_active: agent.last_active,
          liveness: computeLiveness(agent.last_active, now, thresholds),
        }));
    
        const filtered = includeGone
          ? mapped
          : mapped.filter((a) => a.liveness !== "gone");
    
        const activeCount = mapped.filter(
          (a) => a.liveness === "active",
        ).length;
    
        return toolResult({
          agents: filtered,
          total_registered: agents.length,
          active_count: activeCount,
        });
      } catch (e) {
        return toolError(
          e instanceof Error ? e.message : "Unknown error",
          "INTERNAL_ERROR",
        );
      }
    },
  • Input schema for 'twining_agents' tool, defining the optional 'include_gone' boolean parameter.
    inputSchema: {
      include_gone: z
        .boolean()
        .optional()
        .describe(
          "Whether to include gone agents (default: true)",
        ),
    },
  • Registration of the 'twining_agents' tool within the registerCoordinationTools function.
    server.registerTool(
      "twining_agents",
      {
        description:
          "List all registered agents with their capabilities and liveness status.",
        inputSchema: {
          include_gone: z
            .boolean()
            .optional()
            .describe(
              "Whether to include gone agents (default: true)",
            ),
        },
      },
      async (args) => {
        try {
          const includeGone = args.include_gone ?? true;
          const agents = await agentStore.getAll();
          const thresholds =
            config.agents?.liveness ?? DEFAULT_LIVENESS_THRESHOLDS;
          const now = new Date();
    
          const mapped = agents.map((agent) => ({
            agent_id: agent.agent_id,
            capabilities: agent.capabilities,
            role: agent.role,
            description: agent.description,
            registered_at: agent.registered_at,
            last_active: agent.last_active,
            liveness: computeLiveness(agent.last_active, now, thresholds),
          }));
    
          const filtered = includeGone
            ? mapped
            : mapped.filter((a) => a.liveness !== "gone");
    
          const activeCount = mapped.filter(
            (a) => a.liveness === "active",
          ).length;
    
          return toolResult({
            agents: filtered,
            total_registered: agents.length,
            active_count: activeCount,
          });
        } catch (e) {
          return toolError(
            e instanceof Error ? e.message : "Unknown error",
            "INTERNAL_ERROR",
          );
        }
      },
    );
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. It mentions listing agents with 'capabilities and liveness status', which implies a read-only operation, but does not disclose behavioral traits such as permissions needed, rate limits, pagination, or error conditions. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 front-loads the core purpose ('List all registered agents') and adds clarifying details ('with their capabilities and liveness status') without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function.

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 has one parameter with full schema coverage and no output schema, the description is minimally adequate. It states what the tool does but lacks context on usage, behavioral details, or output format, which are important for a tool with no annotations. It meets the threshold for a basic read operation but does not fully compensate for the missing annotations.

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?

The input schema has 100% description coverage, with one parameter ('include_gone') fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 ('List') and resource ('all registered agents'), with additional details about what information is included ('capabilities and liveness status'). It does not explicitly differentiate from sibling tools, but given the sibling list includes many diverse operations (e.g., 'add_entity', 'archive', 'query'), the purpose is sufficiently distinct without explicit comparison.

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 many sibling tools (e.g., 'twining_status', 'twining_recent', 'twining_search_decisions'), there is no indication of context, prerequisites, or exclusions for selecting this tool over others.

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/daveangulo/twining-mcp'

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