Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Add a to-do

connections_todo_add

Use this when the member asks to add, save, note down or remember a to-do, task, reminder or follow-up ('remind me to', 'add X to my list', 'I need to', 'put that on my to-dos'). Creates ONE open to-do on the member's Connections list: in the workspace this connection is bound to when there is one, otherwise in their personal space - the reply names which, so say it back. Keep the title to one line naming the action; put details in body. Not for the assistant's own intended work (that is post_agent_todos_add).

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional details: what, where, who, links.
scopeNoWhere it goes. Default: the bound workspace when this connection has one, else personal.
titleYesOne line naming the action, in the member's words (under ~100 characters).
due_atNoOptional deadline: a day (2026-11-06), or a date-time with the member's UTC offset (2026-11-06T17:00:00-06:00).
labelsNoOptional labels/folders to file it under.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / due_at / description
      Previous value: -"Optional deadline, unix seconds."New value: +"Optional deadline: a day (2026-11-06), or a date-time with the member's UTC offset (2026-11-06T17:00:00-06:00)."
    • addedInput schema / properties / due_at / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2}(\\.\\d{1,9})?)?(Z|[+-]\\d{2}:?\\d{2})?)?$"
    • changedInput schema / properties / due_at / type
      Previous value: -"integer"New value: +"string"
  2. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the cardinality ('ONE open to-do'), the resolution rule for where the record lands (bound workspace, else personal space), and that the reply names the destination so the agent should echo it back. It does not warn about duplicate creation despite idempotentHint=false, which is the one behavioral gap.

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 with the trigger condition, then creation semantics, then a routing exclusion. The parenthetical utterance list is long but functional, and every clause carries usable signal; no filler.

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 7-parameter mutation tool with no output schema, the description covers creation semantics, destination resolution, reply behavior, and the sibling boundary. Only non-idempotency and duplicate handling are unaddressed.

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 explains title, body, scope, due_at, labels, person, and project. The description reinforces the main convention (one-line title naming the action, details in body) and the scope default, but adds little that the schema descriptions do not already carry.

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?

States a specific verb and resource ('Creates ONE open to-do on the member's Connections list') and explicitly excludes the sibling case ('Not for the assistant's own intended work (that is post_agent_todos_add)'). An agent can distinguish this from connections_todo_update, connections_todo_done, and connections_todo_delete on the verb alone.

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?

Gives concrete trigger utterances ('remind me to', 'add X to my list', 'I need to', 'put that on my to-dos') plus an explicit exclusion routing the assistant's own tasks to post_agent_todos_add. Both the when and the when-not are stated rather than implied.

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

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