Skip to main content
Glama

twining_post

Post coordination messages to a shared blackboard for agent collaboration. Share findings, needs, warnings, status updates, and other information with other agents during development tasks.

Instructions

Post an entry to the shared blackboard. Use this to share findings, needs, warnings, status updates, and other coordination messages with other agents. Does NOT accept entry_type 'decision' — use twining_decide instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_typeYesType of blackboard entry
summaryYesOne-line summary (max 200 chars)
detailNoFull context and details
tagsNoDomain tags for filtering
scopeNoFile path, module name, or "project"
relates_toNoIDs of related entries
agent_idNoIdentifier for the posting agent

Implementation Reference

  • Registration of the 'twining_post' tool, which handles the definition of its schema and invokes the 'engine.post' method.
    // twining_post — Post an entry to the shared blackboard
    server.registerTool(
      "twining_post",
      {
        description:
          "Post an entry to the shared blackboard. Use this to share findings, needs, warnings, status updates, and other coordination messages with other agents. Does NOT accept entry_type 'decision' — use twining_decide instead.",
        inputSchema: {
          entry_type: z.enum(ENTRY_TYPES).describe("Type of blackboard entry"),
          summary: z
            .string()
            .max(200)
            .describe("One-line summary (max 200 chars)"),
          detail: z.string().optional().describe("Full context and details"),
          tags: z
            .array(z.string())
            .optional()
            .describe("Domain tags for filtering"),
          scope: z
            .string()
            .optional()
            .describe('File path, module name, or "project"'),
          relates_to: z
            .array(z.string())
            .optional()
            .describe("IDs of related entries"),
          agent_id: z
            .string()
            .optional()
            .describe("Identifier for the posting agent"),
        },
      },
      async (args) => {
        try {
          const result = await engine.post(args);
          return toolResult(result);
        } catch (e) {
          if (e instanceof TwiningError) {
            return toolError(e.message, e.code);
          }
          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?

With no annotations provided, the description carries full burden. It describes the tool's purpose and a key behavioral constraint (no 'decision' entry_type), but doesn't disclose other behavioral traits like authentication requirements, rate limits, side effects, or what happens on success/failure. It adds some context but leaves significant behavioral aspects unspecified.

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?

Two sentences with zero waste. The first sentence establishes purpose and usage context, the second provides a critical exclusion rule. Every word earns its place, and the most important information (what the tool does and a key constraint) is front-loaded.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters, 100% schema coverage, and no output schema, the description provides good contextual completeness. It clearly states the tool's purpose, usage context, and a critical behavioral constraint. However, without annotations or output schema, it could benefit from more information about what happens after posting (e.g., returns an entry ID, confirmation message, etc.).

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 already documents all 7 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 ('Post an entry to the shared blackboard') and resource ('shared blackboard'), with explicit purpose ('to share findings, needs, warnings, status updates, and other coordination messages with other agents'). It distinguishes from sibling 'twining_decide' by excluding 'decision' entry_type.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Use this to share findings, needs, warnings, status updates, and other coordination messages with other agents' and 'Does NOT accept entry_type 'decision' — use twining_decide instead.' This clearly defines when to use this tool versus an alternative.

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