Skip to main content
Glama

Tripwire Ladder

ladder

Tripwire Ladder™: from a free diagnostic to a bigger payment, each rung counted from the product's own people over the last 90 days (days to change it): the diagnostic (its page's visitors, and the signups who used it), signup, the free part used (the activation rule), a first small payment and a bigger one (a second, or a larger one). Returns the definition, the counts, each rung with the share of the rung before that reached it, the rung that keeps the fewest (a missing diagnostic first) and what to build there, with its evidence. With define: what the diagnostic is, read from the code and the site: diagnosticPath (its page, "*" as a wildcard) and or diagnosticEvent (the event the product reports when it runs), and label. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
defineNoWhat the free diagnostic is: its page path and or the event it reports

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, but the description never addresses the write implication — passing 'define' presumably persists the diagnostic definition, yet that side effect and its permanence are not disclosed. On the positive side, the description does detail the return payload (definition, counts, rungs, shares, weakest rung, recommendation, evidence), which is real behavioral value the annotations do not carry.

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

Conciseness2/5

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

The single dense paragraph is hard to parse: parenthetical asides nest inside a list of rungs, and a reader must re-read to separate the ladder definition from the returned fields. It is not padded with filler, but the structure buries key facts (defaults, side effects) behind convoluted clauses rather than front-loading them plainly.

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

Completeness3/5

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

For a parameterized analytics tool with no output schema, the description does cover returned fields at an unusual level of detail, which compensates partly. Yet it omits the 'days' default behavior, whether 'define' persists a configuration, and any cost/rate context beyond 'Free.', so an agent cannot fully predict the call's effect.

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 50%: the nested 'define' object is well documented in the schema and the description reinforces it by explaining diagnosticPath ('*' wildcard) and diagnosticEvent semantics, which adds genuine meaning. However, 'days' has no schema description and the description only implies a 90-day default ('over the last 90 days') without explaining the 14-365 range or what changes when it is set. Baseline 3 for mixed coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific artifact (a 'Tripwire Ladder' funnel from free diagnostic to larger payment) and enumerates its rungs, so the resource is identifiable. But there is no clear verb — it never plainly says 'computes/returns a funnel of conversion steps' — and the phrasing ('each rung counted from the product's own people', 'the rung that keeps the fewest') is idiosyncratic enough that an agent must reconstruct the intent. Distinguishing it from analytics-style siblings is only possible via the Tripwire-specific jargon.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisites, and no mention of any alternative or related tool. The only routing hint is 'Free.', which implies no cost but does not tell the agent when this is the right call versus a general analytics query. The agent is left to infer usage from the name alone.

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