Skip to main content
Glama
Sign In
Kadmia MCP Server

Kadmia MCP Server

by Rakeshpatel87p
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bookmark_concept

Save JavaScript concepts you want to review later. Bookmark a concept, add optional code snippet and notes to track your learning progress.

Instructions

Save a JavaScript concept to study later in the Kadmia app. Use this when you encounter something you want to review or don't fully understand yet.

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": {
      "concept": "<concept>"
    },
    "name": "bookmark_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
conceptYesThe JavaScript concept to bookmark (e.g., 'closures', 'async/await', 'this binding')
code_snippetNoOptional code snippet for context
noteNoOptional note about why you're bookmarking this
sourceNoWhether user bookmarked manually or from a suggestion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only says 'Save' implying mutation but does not disclose any consequences, limits, or persistence details. For a mutation tool, this is insufficient.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose and usage context.

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?

While the description covers purpose and usage, it lacks behavioral transparency (e.g., what happens to existing bookmarks) and does not address the return value (no output schema). For a simple tool, it is adequate but not complete.

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% (all 4 parameters have descriptions), so the baseline is 3. The tool description does not add any extra meaning beyond what the schema already provides.

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 'Save a JavaScript concept to study later' with a specific verb and resource, and it distinguishes from sibling tools (explain_concept, generate_challenge, get_learner_progress) which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear usage context: 'when you encounter something you want to review or don't fully understand yet.' Although it does not explicitly mention when not to use or name alternatives, the context is sufficient given the sibling tools.

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