Skip to main content
Glama
Sign In

Ripplewatch

by ai.ripplewatch
OverviewDiscussionsAdmin

Add a note about the business

add_context_note

Save anything free-form the team knows that no CRM holds, so Ripplewatch can line it up against why deals are lost and what competitors are doing: what they are building and when it ships, a pricing or packaging change, a customer's offhand comment, a sales-call insight, something about the market. Pass the user's words as they said them, with the date if they gave one (effective_on). Unlike set_context it adds a note and never overwrites anything. The more of this, the sharper the answers. It is tagged automatically (what kind, which product areas, which loss themes, when it ships).

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": {
      "note": "<note>"
    },
    "name": "add_context_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesThe note, in the user's own words.
effective_onNoWhen this was true or decided, YYYY-MM-DD. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-destructive, non-open-world writes, and the description corroborates and enriches that with 'never overwrites anything' plus the automatic tagging behavior (kind, product areas, loss themes, ship date) that no structured field reveals. It stops short of saying what the call returns or what happens on validation failure (note is capped at 4000 chars).

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

Conciseness3/5

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

The purpose is front-loaded and the set_context contrast is well placed, but the description runs long and includes promotional padding ('The more of this, the sharper the answers') that doesn't help an agent decide or invoke. The example list is useful yet verbose for a two-parameter tool.

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 simple two-parameter append operation with full schema coverage and no output schema, the description covers what to save, how to phrase it, how dates are handled, and that tagging happens automatically. Only the post-write experience (confirmation/return shape) is unaddressed, which is minor here.

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 meaning: it tells the agent to preserve the user's wording verbatim for 'note' and to only pass effective_on when the user supplied a date, guarding against fabricated dates. That is beyond the schema's format-level description.

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 ('Save anything free-form the team knows that no CRM holds') and immediately distinguishes the tool from a named sibling ('Unlike set_context it adds a note and never overwrites anything'). The concrete example categories (what they are building, pricing changes, sales-call insights) make the scope unmistakable.

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 routes the agent: use this to add, use set_context when overwriting is intended. It also tells the caller how to phrase input ('Pass the user's words as they said them') and what to do with a date the user volunteered, which is exactly the decision an agent faces at invocation time.

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

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