Skip to main content
Glama
datacore-one

datacore-mcp

Official
by datacore-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

datacore_capture

Capture journal entries and knowledge notes to record important decisions, meeting outcomes, and significant events.

Instructions

Capture a journal entry or knowledge note. Call proactively to record important decisions, meeting outcomes, and significant events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoKnowledge note kind: its folder under <space>/3-knowledge/ (atomic idea: zettel; source summary: literature; person/company: reference; wiki page: pages)
tagsNoTags to attach
typeYes
spaceNoSpace to write to, by name or folder (e.g. "team" or "1-team"); default: the personal space
titleNoTitle for knowledge notes
contentYesContent to capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.0
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "Knowledge note kind: its folder under <space>/3-knowledge/ (atomic idea: zettel; source summary: literature; person/company: reference; wiki page: pages)",
+  "enum": [
+    "zettel",
+    "literature",
+    "reference",
+    "pages"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / space
      Added value: +{
+  "description": "Space to write to, by name or folder (e.g. \"team\" or \"1-team\"); default: the personal space",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.6.0

TDQS

B3.3/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. It says 'Capture' but never discloses whether this creates a new file, appends, overwrites on duplicate titles, what permissions are required, or what happens to the entry afterward. For a write operation with zero annotation coverage, this is a meaningful gap.

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?

Two short sentences, zero waste, with the core action front-loaded before the proactive-usage cue. Nothing redundant with the schema.

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?

The schema is rich enough to carry parameter semantics, but for a mutating tool with no annotations and no output schema the description should say more about the write behavior and how it differs from datacore_ingest. Adequate but with a clear completeness gap.

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 83%, above the high-coverage threshold, so the schema already documents kind, space, title, tags and content well. The description adds no parameter-level meaning beyond that, which is the correct baseline when the schema does the heavy lifting.

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 and resource: 'Capture a journal entry or knowledge note.' An agent knows it writes notes. However, it never distinguishes itself from the sibling datacore_ingest, which plausibly also writes content, so the boundary is left ambiguous.

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?

'Call proactively to record important decisions, meeting outcomes, and significant events' gives real usage context, but there are no exclusions and no comparison to alternatives such as datacore_ingest or datacore_search. Usage is implied rather than fully specified.

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