Skip to main content
Glama
Abramov-Front-end

RollDate MCP

by Abramov-Front-end
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_snippet

Generate a ready-to-use JavaScript or HTML snippet for integrating RollDate Core date pickers or Events calendars in a chosen scenario.

Instructions

Get a ready-to-use JS and/or HTML snippet for a RollDate Core or Events scenario.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoSnippet format. Default: both
productNoRollDate product. Default: core (date picker). Use events for event calendars.
scenarioYesScenario id from list_scenarios
assetPathNoRelative path to installed assets. Defaults per product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.2
    • changedInput schema / properties / assetPath / description
      Previous value: -"Relative path to installed assets. Default: vendor/rolldate"New value: +"Relative path to installed assets. Defaults per product."
    • addedInput schema / properties / product
      Added value: +{
+  "description": "RollDate product. Default: core (date picker). Use events for event calendars.",
+  "enum": [
+    "core",
+    "events"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / scenario / description
      Previous value: -"Scenario id. One of: single, single-light, inline, range, range-two, multi, trigger, time-24, time-12, disabled, footer, highlight, range-presets"New value: +"Scenario id from list_scenarios"
    • removedInput schema / properties / scenario / enum
      Removed value: -[
-  "single",
-  "single-light",
-  "inline",
-  "range",
-  "range-two",
-  "multi",
-  "trigger",
-  "time-24",
-  "time-12",
-  "disabled",
-  "footer",
-  "highlight",
-  "range-presets"
-]
  2. Changed2 schema fields changedv1.1.0
    • changedInput schema / properties / scenario / description
      Previous value: -"Scenario id. One of: single, single-light, inline, range, range-two, multi, trigger, time-24, time-12, disabled, footer"New value: +"Scenario id. One of: single, single-light, inline, range, range-two, multi, trigger, time-24, time-12, disabled, footer, highlight, range-presets"
    • changedInput schema / properties / scenario / enum
      Previous value: -[
-  "single",
-  "single-light",
-  "inline",
-  "range",
-  "range-two",
-  "multi",
-  "trigger",
-  "time-24",
-  "time-12",
-  "disabled",
-  "footer"
-]New value: +[
+  "single",
+  "single-light",
+  "inline",
+  "range",
+  "range-two",
+  "multi",
+  "trigger",
+  "time-24",
+  "time-12",
+  "disabled",
+  "footer",
+  "highlight",
+  "range-presets"
+]
  3. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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, and it discloses almost nothing: no statement that this is a pure read/retrieval operation, no side effects, no auth requirements, no note on whether the snippet is generated syntactically or validated against the scenario. 'Ready-to-use' is sales language rather than behavioral fact.

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

Conciseness4/5

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

One front-loaded sentence with no padding or repetition; the purpose lands immediately. It is arguably too terse for a 4-parameter tool, and 'ready-to-use' is filler, but structurally it is clean.

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 simple read tool with no output schema and full schema coverage, the essentials are present and the return artifact (a snippet) is named. Still missing are the usage path (obtain a scenario via list_scenarios first) and any indication of how the fetched snippet should be consumed, which for a snippet-generation tool is meaningful context.

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% and both enums are documented in the schema, so the baseline is 3. The description's 'JS and/or HTML' and 'Core or Events' merely restate the format and product enums without adding syntax, defaulting rationale, or examples beyond what the schema already says.

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 ('Get a ... snippet') and narrows scope to JS/HTML artifacts for RollDate Core or Events scenarios, which maps cleanly onto the product/format parameters. It does not, however, distinguish itself from plausible siblings like scaffold_example or get_install_guide, so an agent must infer the boundary.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as scaffold_example or get_install_guide. The only routing hint ('scenario id from list_scenarios') lives in the schema, not the description, and even that only covers one parameter.

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

Deploy Server

Other Tools