Alcove

Official

by OctopusGarage

Overview Schema Source Related Servers Discussions Admin

Python

Local

alcove_pin_list

Retrieve pinned personal notes filtered by workspace, home, tag, or status to manage important information.

Instructions

List pinned personal notes.

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": "alcove_pin_list"
  }
}

Input Schema

Name	Required	Default
`tag`	No
`home`	No
`status`	No	active
`workspace`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states the action but gives no information about safety, scope, or side effects. This is insufficient for a list operation that may return a large amount of data.

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?

The description is very brief (one sentence), which is concise but at the expense of necessary detail. It is front-loaded but lacks information about parameters and usage.

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 the existence of sibling tools like alcove_pin_search and alcove_pin_get, the description is incomplete. It does not clarify the scope of the list (e.g., all pinned notes, with filtering) or what the output contains, despite an output schema existing.

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

Parameters1/5

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

The input schema has 4 parameters (tag, home, status, workspace) with 0% description coverage. The tool description does not explain any of these parameters, leaving an agent unable to use them correctly.

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 'List pinned personal notes' clearly states the verb (List) and resource (pinned personal notes). It distinguishes from sibling tools like alcove_pin_search (which suggests searching) and alcove_pin_get (getting a specific note).

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like alcove_pin_search or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server