Skip to main content
Glama

get-specific-connector

Retrieve details for a specific connector on a Miro board by providing the board ID and connector ID.

Instructions

Retrieve information about a specific connector on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the connector
connectorIdYesUnique identifier (ID) of the connector that you want to retrieve

Implementation Reference

  • The asynchronous handler function that validates boardId and connectorId, fetches the connector data using MiroClient.getApi().getConnector, stringifies it to JSON, and returns via ServerResponse or handles errors.
    fn: async ({ boardId, connectorId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!connectorId) {
          return ServerResponse.error("Connector ID is required");
        }
    
        const connectorData = await MiroClient.getApi().getConnector(boardId, connectorId);
        return ServerResponse.text(JSON.stringify(connectorData, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
  • Zod schema defining the input parameters: boardId and connectorId as strings with descriptions.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that contains the connector"),
      connectorId: z.string().describe("Unique identifier (ID) of the connector that you want to retrieve")
    },
  • src/index.ts:131-131 (registration)
    Registers the getSpecificConnectorTool with the ToolBootstrapper instance.
    .register(getSpecificConnectorTool)
  • src/index.ts:30-30 (registration)
    Imports the tool definition from its module for registration.
    import getSpecificConnectorTool from './tools/getSpecificConnector.js';
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 information' implies a read-only operation, it doesn't specify permissions required, rate limits, error conditions, or the format/scope of returned information. For a tool with zero 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 is 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (retrieving a specific resource), 100% schema coverage for inputs, no annotations, and no output schema, the description is minimally adequate. It clearly states what the tool does but lacks details on behavior, output, or usage context that would be helpful for an agent.

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 both parameters clearly documented in the schema. The description adds no additional parameter semantics beyond implying that 'boardId' and 'connectorId' are needed to locate the connector. This meets the baseline for high schema coverage.

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 resource 'information about a specific connector on a Miro board', making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'get-connectors' (plural) or 'get-specific-item', but the specificity of 'specific connector' implies a single-item lookup versus a list operation.

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. It doesn't mention sibling tools like 'get-connectors' for listing multiple connectors or 'get-specific-item' for generic item retrieval, nor does it specify prerequisites or contextual constraints 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