Skip to main content
Glama

get-sticky-note-item

Retrieve details for a specific sticky note on a Miro board by providing the board ID and item ID.

Instructions

Retrieve information about a specific sticky note item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the sticky note
itemIdYesUnique identifier (ID) of the sticky note that you want to retrieve

Implementation Reference

  • The main handler function that executes the tool logic. Validates input parameters boardId and itemId, retrieves the sticky note item data via MiroClient API, formats it as JSON, and handles errors using ServerResponse.
    fn: async ({ boardId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const stickyNoteData = await MiroClient.getApi().getStickyNoteItem(boardId, itemId);
        return ServerResponse.text(JSON.stringify(stickyNoteData, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including name, description, and Zod-based input schema for boardId and itemId parameters.
    const getStickyNoteItemTool: ToolSchema = {
      name: "get-sticky-note-item",
      description: "Retrieve information about a specific sticky note item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the sticky note"),
        itemId: z.string().describe("Unique identifier (ID) of the sticky note that you want to retrieve")
      },
  • src/index.ts:135-135 (registration)
    Registration of the getStickyNoteItemTool in the ToolBootstrapper chain.
    .register(getStickyNoteItemTool)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a retrieval operation, implying read-only behavior, but doesn't disclose any behavioral traits such as authentication needs, rate limits, error conditions, or what information is returned (e.g., content, metadata). This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the core action.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what information is retrieved (e.g., text, color, position) or behavioral aspects like permissions. For a retrieval tool with rich sibling context, this minimal description leaves too many open questions.

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%, with clear documentation for both parameters (boardId and itemId). The description adds no additional meaning beyond the schema, such as format examples or constraints. Baseline 3 is appropriate 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?

The description clearly states the verb 'retrieve' and the resource 'sticky note item on a Miro board', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-specific-item' or 'get-items-on-board' that might also retrieve sticky notes, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-specific-item' (which might retrieve any item type) or 'get-items-on-board' (which retrieves multiple items). There's no mention of prerequisites, exclusions, or specific contexts for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-jarzyna/mcp-miro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server