Skip to main content
Glama
Sign In

Ripplewatch

by ai.ripplewatch
OverviewDiscussionsAdmin

Competitor detail

get_competitor
Read-only

Full detail on one tracked competitor: momentum label, score and confidence with the per-input drivers behind it (hiring, pricing, reviews and so on), the 10 most recent scored signals, and counts of deals won and lost or churned against them. Use it when the user asks about a specific competitor, for example 'Is Northlane heating up?'; use get_momentum to compare all of them at once. An unknown name returns an error that lists the tracked competitors. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompetitor name, case-insensitive, exactly as returned by list_competitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Competitor name, as returned by list_competitors."New value: +"Competitor name, case-insensitive, exactly as returned by list_competitors."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds useful behavior beyond that — an unknown name returns an error that enumerates the tracked competitors, and signal retrieval is bounded to the 10 most recent. It does not mention any paging or rate characteristics, but for a read-only single-record fetch those are minor.

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?

A single tight block: payload contents first, then when to use, then the sibling alternative, then the error case. Every sentence carries information and the most decision-relevant content is front-loaded.

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?

With no output schema, the description compensates by enumerating the returned sections (momentum, confidence, drivers, recent signals, deal counts). Combined with the error-case disclosure for a single-parameter read-only tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100% and the only parameter's description already states case-insensitivity and the list_competitors provenance. The description's mention of "unknown name returns an error" adds slight value but no new syntax or format guidance, so 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?

Names a specific verb and resource ("Full detail on one tracked competitor") and enumerates exactly what that detail contains: momentum label, score, confidence, per-input drivers, 10 recent signals, and win/loss/churn counts. It is clearly distinguishable from get_momentum, which is described as the comparison view.

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?

States the triggering condition ("when the user asks about a specific competitor") with a concrete example query, and names the alternative (get_momentum) plus the condition that selects it. Nothing is left to inference.

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