Skip to main content
Glama

twining_register

Register or update agents in the Twining MCP Server to make subagents visible in the coordination dashboard and merge capabilities during re-registration.

Instructions

Register a new agent or update an existing one. Merges capabilities on re-registration. Use this to make subagents visible in the coordination dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesUnique identifier for the agent (e.g. 'code-reviewer', 'test-runner')
capabilitiesNoAgent capabilities (e.g. ['testing', 'typescript'])
roleNoAgent role (e.g. 'reviewer', 'implementer')
descriptionNoHuman-readable description of what the agent does

Implementation Reference

  • The implementation of the `twining_register` tool, which registers or updates an agent in the registry using the agentStore and optionally populates a graph.
    // twining_register — Register or update an agent in the registry
    server.registerTool(
      "twining_register",
      {
        description:
          "Register a new agent or update an existing one. Merges capabilities on re-registration. Use this to make subagents visible in the coordination dashboard.",
        inputSchema: {
          agent_id: z
            .string()
            .describe("Unique identifier for the agent (e.g. 'code-reviewer', 'test-runner')"),
          capabilities: z
            .array(z.string())
            .optional()
            .describe("Agent capabilities (e.g. ['testing', 'typescript'])"),
          role: z
            .string()
            .optional()
            .describe("Agent role (e.g. 'reviewer', 'implementer')"),
          description: z
            .string()
            .optional()
            .describe("Human-readable description of what the agent does"),
        },
      },
      async (args) => {
        try {
          const record = await agentStore.upsert({
            agent_id: args.agent_id,
            capabilities: args.capabilities,
            role: args.role,
            description: args.description,
          });
          // Auto-populate graph with agent entity
          if (graphPopulator) {
            await graphPopulator.onRegister(args.agent_id, args.capabilities, args.role);
          }
          return toolResult({
            agent_id: record.agent_id,
            capabilities: record.capabilities,
            role: record.role,
            description: record.description,
            registered_at: record.registered_at,
            last_active: record.last_active,
          });
        } catch (e) {
          return toolError(
            e instanceof Error ? e.message : "Unknown error",
            "INTERNAL_ERROR",
          );
        }
      },
    );
Behavior3/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 discloses key behavioral traits: it can create or update agents, merges capabilities on re-registration, and affects dashboard visibility. However, it lacks details on permissions, error handling, or response format, which are important for a mutation tool.

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 front-loaded with the core purpose in the first sentence, followed by a specific usage guideline. Both sentences are essential and waste no words, making it highly efficient and well-structured.

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?

For a mutation tool with no annotations and no output schema, the description is adequate but incomplete. It covers the purpose and basic behavior but lacks details on return values, error conditions, or side effects, which are crucial for an agent to use it correctly.

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 description coverage is 100%, so the schema fully documents all parameters. The description does not add any additional meaning or examples beyond what the schema provides, such as clarifying how merging works or typical use cases for each parameter.

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 action ('register a new agent or update an existing one'), specifies the resource ('agent'), and distinguishes it from siblings by mentioning the coordination dashboard visibility, which is unique among the listed sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when to use the tool ('to make subagents visible in the coordination dashboard') and implies usage for both new registration and updates. However, it does not explicitly state when not to use it or name alternatives among siblings, such as twining_agents for listing agents.

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