Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Save a note

connections_note_save

Use this when the member asks to save, write down, jot or note something ('save this', 'make a note of that', 'write this down'). Creates ONE new note 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 thing; put the rest of the content in body. Not for a task or reminder - use connections_todo_add for those.

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional: the note's content.
scopeNoWhere it goes. Default: the bound workspace when this connection has one, else personal.
titleYesOne line naming the note, in the member's words (under ~100 characters).
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. 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-idempotent, non-destructive. The description adds real value beyond that: the routing rule (bound workspace else personal space) and the fact that the reply names the destination, which the agent should echo back. It stops short of warning that repeated calls create duplicates, which matters given idempotentHint=false.

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 destination behavior, then formatting guidance, then exclusion. Dense but every sentence carries information; only slight compression is possible.

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?

No output schema, yet the description covers the one return detail that matters (the reply states which scope the note landed in). With 6 params fully documented in schema and annotations covering safety, remaining gaps are minor, mainly duplicate-creation behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine guidance: keep title to one line naming the thing and move remaining content into body. That shapes how title and body are split in a way the schema text alone does not.

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 new note on the member's Connections list') and explicitly disambiguates from note-appending and from todo/reminder creation. The 'ONE new note' framing separates it from connections_notes_append_to_note without needing the sibling schema.

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 user trigger phrases ('save this', 'make a note of that', 'write this down') and names the exclusion plus the correct alternative: 'Not for a task or reminder - use connections_todo_add for those.' Both when and when-not are explicit.

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