Skip to main content
Glama

Set notes for AI

set_instructions
DestructiveIdempotent

Replace the connection's notes for AI: the guidance every AI tool receives from get_context, such as "Amounts are in cents" or "Use orders_v2, not orders". Call get_context first and send the full new text, since this replaces the notes rather than appending. An empty string clears them. Changes what every AI tool and person on this connection reads, and is recorded in SaturnSQL with your name. Only make it when the user asked for it or confirmed it. Needs the write scope, the connection's owner or an admin, and a plan that includes Context.

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": {
      "connectionId": "<connectionId>",
      "instructions": "<instructions>"
    },
    "name": "set_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesConnection id from list_connections.
instructionsYesThe complete notes, as plain text.

Output Schema

NameRequiredDescriptionDefault
updatedAtNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: replace-not-append semantics, empty string clears, blast radius ('changes what every AI tool and person on this connection reads'), audit logging ('recorded in SaturnSQL with your name'), and the full permission/plan requirements. destructiveHint=true is consistent with and enriched by this text.

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 action and resource, then prerequisites, side effects, and permissions in a logical order. It is a dense single paragraph with no filler sentences, though the permission clause could be split out for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values need no explanation, and everything an agent needs to call this safely is present: prerequisites, replace semantics, clearing behavior, authorization scope, plan gating, and audit consequences. Nothing material is missing for a two-parameter mutation tool.

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 the baseline is 3, but the description adds real meaning: instructions must be the complete text (not a patch) and an empty string is a valid value that clears the notes. It does not restate connectionId's origin beyond what the schema explains.

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 ('Replace the connection's notes for AI') and immediately defines the resource in operational terms ('the guidance every AI tool receives from get_context'), with concrete examples of the content. An agent can distinguish this from get_context without opening either 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?

Explicitly names the prerequisite alternative ('Call get_context first') and the reason for it, and gives an authorization gate for when to invoke ('Only make it when the user asked for it or confirmed it'). Both when-to-use and when-not-to-act are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources