Skip to main content
Glama
Sign In

Ripplewatch

by ai.ripplewatch
OverviewDiscussionsAdmin

Log competitor mentions from sales calls

log_call_mentions

Record times a tracked competitor came up on a sales call. Pass only short verbatim snippets the user has given you (a sentence or two) of where the competitor was mentioned, never full transcripts. If all you have is a summary, pass a one-sentence summary and say it is a summary. Mentions of competitors that aren't tracked are reported back, not guessed. Ask the user before logging, and never invent a quote or a mention. Repeats are ignored, so sending the same mention again is safe.

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": {
      "mentions": "<mentions>"
    },
    "name": "log_call_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
mentionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already indicate a non-read-only, non-destructive, closed-world mutation. The description adds important behavioral context beyond that: repeats are ignored so resubmission is safe, untracked competitors are reported back rather than guessed, and user confirmation is required before logging.

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?

The description is front-loaded with the core action and then layers on the most important safety and input-quality rules. Each sentence contributes a distinct operational constraint, and there is 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 single-parameter logging tool with no output schema, the description covers the essential input rules, safety constraints, idempotency behavior, and handling of untracked competitors. It does not describe the success response or any partial-failure behavior, which is a minor remaining gap.

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?

Although the context reports 0% schema description coverage, the description substantively explains what to supply in the mentions parameter: short verbatim snippets or a one-sentence summary, with an explicit prohibition against invented quotes. It does not cover constraints such as the 500-character quote limit or the maximum number of mentions.

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?

The description states a specific verb and resource: recording times a tracked competitor was mentioned on a sales call. It distinguishes this from broader feedback or win/loss logging by emphasizing competitor mentions and the tracked-competitor scope.

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?

It gives explicit usage rules: pass only short verbatim snippets, never full transcripts, use a one-sentence summary when needed, ask the user before logging, and never invent a quote. It also explains what happens with untracked competitors and repeated mentions.

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