Skip to main content
Glama
Sign In

dialogbrain

by com.dialogbrain
OverviewDiscussionsAdmin

folders_create

📁 Create a new inbox folder to organize threads.

When to use:

  • User wants to create a folder to group related conversations

  • User wants to organize threads by topic, project, or contact type

After creating a folder, use threads.update with folder_id to move threads into it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "folders_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoEmoji icon for the folder (max 10 chars, optional)
nameYesFolder name (max 100 chars)
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety and non-idempotency are covered structurally. The description adds useful post-create workflow guidance (folder_id → threads.update) but says nothing about permissions, duplicate-name behavior, or what the folder object contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-line purpose followed by a short when-to-use list and a single next-step sentence; nothing is padded. Slight overhead from the emoji prefix, but the structure is clean and scannable.

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 create tool with no output schema, the description covers intent, trigger conditions, and the follow-up action, and annotations cover the safety profile. The only meaningful gap is what the call returns (presumably a folder id, only implied by the threads.update instruction).

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%, with name, icon and in_workspace all documented inline including length limits and workspace semantics. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Create a new inbox folder to organize threads'), which is unambiguous and distinct from the sibling folders_delete. It does not, however, explicitly name or contrast any sibling, so differentiation is inferred rather than stated.

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?

Includes an explicit 'When to use' block with two concrete conditions (grouping related conversations, organizing by topic/project/contact type) plus a follow-up instruction to move threads via threads.update with folder_id. It gives clear context but no exclusions or alternative-tool routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources