Skip to main content
Glama
Sign In
Jarvis Markdown MCP

Jarvis Markdown MCP

by ash25082003
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_reminder

Add a task to REMINDERS.md with an optional local due date and time to track reminders.

Instructions

Add a task to REMINDERS.md, optionally with a local due date and time.

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": {
      "task": "<task>"
    },
    "name": "add_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoOptional local date and time in YYYY-MM-DD HH:MM format.
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 should disclose behavioral traits. It only states 'Add a task to REMINDERS.md' without explaining side effects (e.g., appending vs overwriting), permissions, or return behavior.

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

Conciseness3/5

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

A single sentence with 13 words is concise, but it sacrifices detail. It is appropriately front-loaded but could benefit from adding behavioral context without becoming verbose.

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?

Given no output schema and minimal annotations, the description lacks completeness. It does not explain return values, confirmation of success, or any constraints (e.g., file format, overwrite behavior).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (only 'due' has a description). The tool description adds minimal value beyond the schema, simply restating that the due date is optional.

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

Purpose5/5

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

The description clearly states the action ('Add') and the target resource ('a task to REMINDERS.md'), distinguishing it from sibling tools like 'complete_reminder' and 'list_reminders'.

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 explicit guidance on when to use this tool versus alternatives. The description only mentions an optional parameter but does not provide context for usage decisions.

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