Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__tasks_create

Create one task, or many tasks in one call. Pass title (with notes and due) for one task, or tasks for several: each task is inserted into the shared task list, or into its own tasklist_id where it names one, and the response carries one outcome per task in order (results[]: index, title, ok, id or error) so a partial batch is visible. Create every task of a run in one call rather than one call per task. Give title or tasks, not both.

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": {
      "tasklist_id": "<tasklist_id>"
    },
    "name": "gws-mcp__tasks_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoDue date in RFC 3339 format (e.g., 2026-03-28T00:00:00Z)
notesNoNotes/description for the task
tasksNoSeveral tasks created in one request, in this order. Each carries its own title, optional notes and due, and may name its own tasklist_id; otherwise the shared tasklist_id applies. Give title or tasks, not both.
titleNoTitle of the task, for the one-task case. Give title or tasks, not both.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
tasklist_idYesThe task list ID (or '@default' for the default list). The shared list for a tasks batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare a non-destructive write; the description goes further by disclosing the resolution rule for the shared tasklist_id versus a per-task tasklist_id, the order-preserving per-task outcome array (index, title, ok, id or error), and that partial batches are visible. That partial-failure behavior is exactly the trait an agent needs before attempting a multi-task insert.

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?

Single dense paragraph, front-loaded with the primary action and followed by mode semantics and the exclusivity rule. It is efficient, though the parenthetical enumeration of results[] fields makes the middle clause slightly run-on.

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?

With no output schema, the description correctly compensates by describing the results[] payload shape and ordering. For a dual-mode tool with a nested array parameter it is nearly complete, but it leaves open whether a failure aborts remaining tasks and whether there is a batch size limit.

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 title, tasks, notes, due, account, and tasklist_id are already documented in the schema, including the per-task tasklist_id override. The description restates the title-vs-tasks exclusion that the schema properties already carry, adding little new meaning beyond the structured fields.

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 opening sentence names a specific verb and resource ("Create one task, or many tasks in one call") and immediately distinguishes the two operating modes. An agent can tell this apart from tasks_update, tasks_complete, tasks_list_tasks, and tasks_create_tasklist without opening any schema.

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 gives an explicit batching directive ("Create every task of a run in one call rather than one call per task") and an explicit exclusivity rule ("Give title or tasks, not both"). What is missing is routing to sibling alternatives, e.g. that creating a new list requires tasks_create_tasklist, so an agent still has to infer the when-not case.

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

All DataToRAG 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