Skip to main content
Glama

get-app-card-item

Retrieve detailed information about a specific app card item on a Miro board by providing the board ID and item ID.

Instructions

Retrieve information about a specific app card item on a Miro board

Input Schema

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

Implementation Reference

  • The handler function that executes the tool logic: validates boardId and itemId, fetches the app card item data from Miro API, and returns it as formatted JSON or an error response.
    fn: async ({ boardId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const itemData = await MiroClient.getApi().getAppCardItem(boardId, itemId);
    
        return ServerResponse.text(JSON.stringify(itemData, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including the tool name, description, and input schema using Zod for boardId and itemId parameters.
    const getAppCardItemTool: ToolSchema = {
      name: "get-app-card-item",
      description: "Retrieve information about a specific app card item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the app card"),
        itemId: z.string().describe("Unique identifier (ID) of the app card that you want to retrieve")
      },
  • src/index.ts:122-122 (registration)
    The registration of the getAppCardItemTool with the ToolBootstrapper in the main index file.
    .register(getAppCardItemTool)
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 burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what information is returned (e.g., fields, format). For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place with no 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?

Given the tool's low complexity (2 simple parameters) and high schema coverage, the description is minimally adequate. However, with no output schema and no annotations, it should ideally provide more context about return values or behavioral traits. It meets basic requirements but lacks depth for full agent understanding.

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?

The input schema has 100% description coverage, clearly documenting both parameters (boardId and itemId). The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as 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 'information about a specific app card item on a Miro board', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get-card-item' or 'get-specific-item', which appear to retrieve similar resources, so it falls short of 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. With sibling tools like 'get-card-item', 'get-specific-item', and 'get-items-on-board' available, there's no indication of how this tool differs in scope or when it should be preferred, leaving the agent without usage context.

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