Skip to main content
Glama

Visibility Genies

Add a note to an action

add_action_note

Add a note or comment to a saved action, shown with the action as added by your agent. Notes are kept; they cannot be edited or removed here. Uses no credits or provider calls.

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": {
      "projectId": "<projectId>",
      "id": "<id>",
      "text": "<text>"
    },
    "name": "add_action_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
textYesThe note, at most 2000 characters.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not destructive, closed-world). The description goes beyond them by disclosing that notes are append-only and cannot be edited or removed here, that they are visibly attributed to the agent, and that the call consumes no credits or provider calls — real cost and irreversibility context.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the action, followed by the durability constraint and the cost note. Nothing is repeated from the title and no filler remains.

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 an output schema available and full schema coverage, the description covers the essential unknowns: permanence, attribution, and zero cost. Only minor gaps remain, such as whether the note is visible externally or ordered relative to existing notes.

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%, and the schema already explains id, text (including the 2000-char cap) and projectId with a pointer to list_projects. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Add a note or comment to a saved action') plus the attribution model ('as added by your agent'). An agent can distinguish this write-a-note tool from edit_action or update_action without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case (appending commentary to an existing saved action) and warns that notes are permanent, which steers behavior. It never explicitly contrasts with siblings like edit_action or update_action, nor states a when-not-to-use condition, so guidance is implied rather than stated.

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