Skip to main content
Glama

twining_recent

Retrieve recent blackboard entries to monitor agent coordination activity and track decisions without applying filters.

Instructions

Get the most recent blackboard entries. Quick way to see latest activity without specifying filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoNumber of entries to return (default: 20)
entry_typesNoOptional type filter

Implementation Reference

  • The MCP tool handler for 'twining_recent', which invokes the engine's recent method.
    async (args) => {
      try {
        const result = await engine.recent(args.n, args.entry_types);
        return toolResult(result);
      } catch (e) {
        return toolError(
          e instanceof Error ? e.message : "Unknown error",
  • The 'recent' method in BlackboardEngine which retrieves the most recent blackboard entries.
    /** Get the N most recent entries, optionally filtered by type. */
    async recent(
      n?: number,
      entry_types?: string[],
    ): Promise<{ entries: BlackboardEntry[] }> {
      const entries = await this.store.recent(n, entry_types);
      return { entries };
    }
  • The registration of the 'twining_recent' tool in the MCP server.
    server.registerTool(
      "twining_recent",
      {
        description:
          "Get the most recent blackboard entries. Quick way to see latest activity without specifying filters.",
        inputSchema: {
          n: z
            .number()
            .optional()
            .describe("Number of entries to return (default: 20)"),
          entry_types: z
            .array(z.string())
            .optional()
            .describe("Optional type filter"),
        },
      },
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 mentions 'most recent' and 'quick way,' which adds some behavioral context about speed and recency, but lacks details on permissions, rate limits, or what 'blackboard entries' entail. It doesn't contradict annotations, but could be more informative for a read operation.

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 two concise sentences with zero waste. It front-loads the core purpose and follows with usage context, making it easy to scan and understand quickly.

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 read tool with 2 parameters and no output schema, the description is adequate but has gaps. It explains the purpose and usage well, but lacks details on return values or error handling. Given the simplicity and high schema coverage, it's minimally complete but could benefit from more behavioral context.

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 both parameters (n and entry_types). The description adds marginal value by implying 'without specifying filters' relates to entry_types, but doesn't provide additional syntax or format details beyond what the schema offers. Baseline 3 is appropriate given high schema coverage.

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 tool's purpose: 'Get the most recent blackboard entries' specifies the verb (get) and resource (blackboard entries). It distinguishes from siblings like twining_search_decisions or twining_query by emphasizing 'most recent' and 'without specifying filters,' though it doesn't explicitly name alternatives.

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?

The description provides clear context for when to use this tool: 'Quick way to see latest activity without specifying filters.' This implies it's for quick overviews rather than detailed queries, but it doesn't explicitly state when not to use it or name specific sibling alternatives like twining_query for filtered searches.

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