Skip to main content
Glama
Abramov-Front-end

RollDate MCP

by Abramov-Front-end
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

install_assets

Copy RollDate Core or Events CSS/JS into the current project to integrate the scrolling date picker or event calendar assets.

Instructions

Copy RollDate Core or Events CSS/JS into the current project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productNoRollDate product. Default: core (date picker). Use events for event calendars.
targetDirNoDestination folder relative to project cwd. Defaults per product.
includeReadableNoAlso copy non-minified Core files. Default: false. Events ignores this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.2
    • changedInput schema / properties / includeReadable / description
      Previous value: -"Also copy non-minified rolldate.js / rolldate.css. Default: false"New value: +"Also copy non-minified Core files. Default: false. Events ignores this."
    • 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 / targetDir / description
      Previous value: -"Destination folder relative to project cwd. Default: vendor/rolldate"New value: +"Destination folder relative to project cwd. Defaults per product."
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and largely fails: it does not say whether existing files are overwritten, whether directories are created, whether an existing project/config is required, or how errors surface. For a filesystem-writing operation, the destructive/overwrite semantics are undisclosed.

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?

A single short sentence with the verb and resource front-loaded and no filler. It is efficient but so terse that it omits necessary context, which is penalized elsewhere rather than here.

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

Completeness2/5

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

For a zero-required-param installer with no annotations and no output schema, the description should at least indicate what ends up where, that it writes into the project, and any overwrite behavior. None of that is present, leaving the agent dependent entirely on the schema.

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 product, targetDir, and includeReadable are already well documented in the schema (including the 'Events ignores this' caveat). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb (Copy) and resource (RollDate Core or Events CSS/JS) with the destination implied as the current project. It implicitly distinguishes itself from siblings like install_agent_rules and scaffold_example by naming CSS/JS assets, though it never explicitly differentiates them.

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?

No guidance on when to choose this over get_install_guide, scaffold_example, or install_agent_rules, and no prerequisites or sequencing (e.g., run before or after scaffolding). The only usage hints live in the schema parameter descriptions, not the tool description.

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