Create a pinned personal note with title, content, tags, priority, and resources to organize and highlight key information in Alcove.
Create a pinned personal note.
| Name | Required | Description | Default |
|---|---|---|---|
| home | No | ||
| kind | No | regular | |
| tags | No | ||
| title | Yes | ||
| content | No | ||
| summary | No | ||
| priority | No | medium | |
| resources | No | ||
| workspace | No | ||
| description | No | ||
| source_refs | No | ||
| content_format | No | text |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full burden. It merely states creation without disclosing side effects, requirements, or constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (4 words), front-loaded, but lacks the substance needed for a tool with many parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (12 parameters, no schema descriptions, no annotations), the description is completely inadequate and does not explain what a pinned note is or how to use the parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, requiring the description to compensate, but it provides no information about any of the 12 parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Create a pinned personal note' clearly states the verb (create) and resource (pinned personal note), but does not explicitly distinguish it from sibling tools like alcove_pin_update or alcove_pin_get.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor any scenarios or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/OctopusGarage/alcove'
If you have feedback or need assistance with the MCP directory API, please join our Discord server