Skip to main content
Glama

get_component_native_notes

Retrieve platform-specific developer notes for native iOS or Android components to understand implementation details and accessibility requirements.

Instructions

Get platform-specific developer notes for native components (iOS or Android implementation details).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesNative platform (ios or android)
componentYesComponent name (e.g., "button", "switch")

Implementation Reference

  • Main handler function for get_component_native_notes tool. Fetches platform-specific (iOS/Android) developer notes for native components using ContentLoader, includes error handling with suggestions.
    async function handleGetComponentNativeNotes(args: any) {
      try {
        const format = args.platform === 'ios' ? 'iosDeveloperNotes' : 'androidDeveloperNotes';
        const content = await contentLoader.getComponentContent('native', args.component, format);
        return {
          content: [
            {
              type: 'text',
              text: content,
            },
          ],
        };
      } catch (error: any) {
        const suggestions = contentLoader.getSimilarComponents('native', args.component);
        const formats = contentLoader.getAvailableFormats('native', args.component);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(
                {
                  error: error.message,
                  component: args.component,
                  platform: args.platform,
                  suggestions,
                  availableFormats: formats,
                },
                null,
                2
              ),
            },
          ],
          isError: true,
        };
      }
    }
  • Tool schema definition including name, description, and input schema requiring 'platform' (ios/android) and 'component'.
    {
      name: 'get_component_native_notes',
      description: 'Get platform-specific developer notes for native components (iOS or Android implementation details).',
      inputSchema: {
        type: 'object',
        properties: {
          platform: {
            type: 'string',
            enum: ['ios', 'android'],
            description: 'Native platform (ios or android)',
          },
          component: {
            type: 'string',
            description: 'Component name (e.g., "button", "switch")',
          },
        },
        required: ['platform', 'component'],
      },
    },
  • src/index.ts:36-40 (registration)
    Registers all tools including get_component_native_notes by returning TOOL_DEFINITIONS in the ListToolsRequest handler for the stdio MCP server.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOL_DEFINITIONS,
      };
    });
  • src/index.ts:68-69 (registration)
    Dispatches calls to the get_component_native_notes handler in the CallToolRequest switch statement.
    case 'get_component_native_notes':
      return await handleGetComponentNativeNotes(args);
  • Duplicate inline handler for Netlify HTTP transport, similar logic without full error handling.
    case 'get_component_native_notes': {
      const format = args.platform === 'ios' ? 'iosDeveloperNotes' : 'androidDeveloperNotes';
      const content = await contentLoader.getComponentContent('native', args.component, format);
      return { content: [{ type: 'text', text: content }] };
    }
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. It mentions retrieving notes but doesn't cover aspects like whether this is a read-only operation, potential rate limits, authentication needs, error handling, or what the return format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose without unnecessary words. Every part earns its place by specifying what is retrieved and the scope, making it easy to parse quickly.

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 (2 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral traits, and output, which are needed for a complete understanding. Without annotations or output schema, more elaboration would be beneficial.

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 schema description coverage is 100%, with clear descriptions for both parameters ('platform' and 'component'), including an enum for 'platform'. The description adds minimal value beyond the schema by specifying 'iOS or Android' and 'developer notes', but doesn't provide additional syntax, format details, or examples. 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 tool's purpose with a specific verb ('Get') and resource ('platform-specific developer notes for native components'), and specifies the scope ('iOS or Android implementation details'). However, it doesn't explicitly differentiate from sibling tools like 'get_component_developer_notes' or 'get_native_component', which appear related.

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 multiple sibling tools involving components and notes (e.g., 'get_component_developer_notes', 'get_native_component'), there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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/joe-watkins/magentaa11y-mcp-remote'

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