Skip to main content
Glama
Sign In

QuietDiff

by com.quietdiff
OverviewDiscussionsAdmin

create_from_template

Creates a monitor from a pre-built template with optional custom selectors. The result includes the initial fetch and what matched. JavaScript rendering (renderJs) is available on Starter+.

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": {
      "templateId": "<templateId>",
      "url": "<url>"
    },
    "name": "create_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to monitor
nameNoOptional custom name (defaults to template name)
fieldsNoOptional custom fields that override template defaults. CSS selectors or JSON paths. When omitted, the monitor watches main content.
waitForNoFor renderJs: "networkidle" or CSS selector
renderJsNoEnable JavaScript rendering (Starter+, hourly min)
templateIdYesTemplate ID from list_templates
checkIntervalNoOptional check interval in seconds. A value faster than the plan minimum is rejected. When omitted, Free stays on the daily minimum and faster plans keep the hourly template default when the plan allows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / checkInterval / description
      Previous value: -"Optional check interval in seconds (defaults to 3600, 3600+ for JS)"New value: +"Optional check interval in seconds. A value faster than the plan minimum is rejected. When omitted, Free stays on the daily minimum and faster plans keep the hourly template default when the plan allows it."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the result includes the initial fetch and what matched, plus the Starter+ requirement for renderJs, but it omits permissions, monitor state after creation, side effects, and failure behavior.

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 three concise sentences, front-loaded with the core action and followed by result and plan details. Every sentence adds useful information without repetition.

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 seven-parameter mutation tool with no annotations and no output schema, the description is only partially complete. It gives a high-level return summary and plan note but omits permissions, side effects, error conditions, and a fuller return description.

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%, so the schema already documents all seven parameters thoroughly. The description adds only minimal meaning beyond that, referring to optional custom selectors and the renderJs plan restriction.

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

Purpose4/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: "Creates a monitor from a pre-built template with optional custom selectors." This clearly distinguishes template-based creation from generic monitor creation, though it does not explicitly name create_monitor as the alternative.

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?

Usage is implied by the template-based framing, and the renderJs plan constraint is stated. However, there is no explicit guidance on when to choose this tool over create_monitor, nor are prerequisites such as listing templates first described.

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

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