Retrieve instance methods and properties for RollDate Core or Events to help AI agents integrate the vanilla JS date picker or calendar.
Return instance methods and properties for RollDate Core or Events.
| Name | Required | Description | Default |
|---|---|---|---|
| product | No | RollDate product. Default: core (date picker). Use events for event calendars. |
Changes observed during successful MCP inspections.
v1.3.2Input schema / additionalPropertiesAdded value: +falseInput schema / properties / productAdded value: +{
+ "description": "RollDate product. Default: core (date picker). Use events for event calendars.",
+ "enum": [
+ "core",
+ "events"
+ ],
+ "type": "string"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not state whether the result is static reference documentation, whether it requires a prior install, or how the output is structured. For a read-only reference tool the bar is modest, but the description adds essentially no behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence that is front-loaded and waste-free. It is appropriately sized for a simple one-parameter lookup tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only lookup with full schema coverage and no output schema, the description is minimally adequate but omits what the returned methods/properties are used for and how they relate to the installation workflow it likely supports. A bit more context would make it genuinely useful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter's enum is fully documented in the schema, including the default. The description names the two products, which matches the schema content, so it adds little beyond it. Baseline 3 for high schema coverage is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb+resource: 'Return instance methods and properties' for two named products (RollDate Core or Events). It distinguishes itself reasonably as a documentation/API-lookup tool versus siblings like get_options or get_snippet. The purpose is clear, though it doesn't explicitly differentiate from the closest sibling get_options.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no comparison to alternatives like get_options or get_snippet, and no mention of prerequisites. The agent gets a resource but no routing signals for when this lookup is the right call versus siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.