Skip to main content
Glama
Sign In
Keep It MCP Server

Keep It MCP Server

by sglewis100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

keepit_get_current_item

Retrieve the active or frontmost item currently open in Keep It so AI agents can identify and work with the note or document in focus.

Instructions

Get the active or frontmost item currently open in Keep It.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keepit_get_current_item"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 implies a read, but does not disclose what happens when no item is open (null, error, empty result), whether it depends on the app being frontmost/focused, or any permission requirements.

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?

A single front-loaded sentence that identifies the resource and its scoping qualifier with no filler or redundancy.

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?

For a zero-parameter read with no output schema, the description says what is fetched but not what is returned (item shape) or what occurs when nothing is open. Adequate for a simple accessor, but the edge-case and focus-dependency behavior an agent would want is absent.

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

Parameters4/5

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

The tool takes zero parameters and the schema is trivially empty with 100% coverage, so there is nothing for the description to clarify. Baseline 4 applies for a no-parameter tool.

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 ('Get') and a clearly bounded resource ('the active or frontmost item currently open in Keep It'). The phrase 'active or frontmost' implicitly separates it from the sibling keepit_get_selected_items, but the description never names or contrasts that sibling explicitly, so the differentiation is inferred rather than stated.

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 when-to-use, when-not-to-use, or alternative guidance is given. With keepit_get_selected_items and keepit_get_item in the sibling list, an agent has to guess whether 'current' means frontmost window, last-edited, or something else, and when to prefer one accessor over another.

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