Skip to main content
Glama
sgup
by sgup

get_icon

Retrieve detailed information about a specific icon from The Noun Project by its unique ID, including metadata, creator details, tags, and download URLs.

Instructions

Get detailed information about a specific icon by its ID. Returns icon metadata, creator info, tags, and download URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icon_idYesThe unique ID of the icon
thumbnail_sizeNoThumbnail size to return (42, 84, or 200 pixels)

Implementation Reference

  • Core handler function that fetches detailed information about a specific icon by ID from the Noun Project API, handling thumbnail size parameter and OAuth headers.
    async getIcon(params: GetIconParams) {
      const { icon_id, thumbnail_size } = params;
      const queryParams = thumbnail_size
        ? `?thumbnail_size=${thumbnail_size}`
        : '';
      const url = `${BASE_URL}/v2/icon/${icon_id}${queryParams}`;
      const headers = this.oauth.getHeaders(url);
    
      const response = await this.client.get(`/v2/icon/${icon_id}`, {
        params: thumbnail_size ? { thumbnail_size } : undefined,
        headers,
      });
    
      return response.data;
    }
  • MCP server tool dispatch handler for 'get_icon', calling the API method and formatting the response as MCP content.
    case 'get_icon': {
      const result = await api.getIcon(args as any);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/tools.ts:49-68 (registration)
    Tool registration in the TOOLS array, including name, description, and input schema for MCP listTools response.
    {
      name: 'get_icon',
      description:
        'Get detailed information about a specific icon by its ID. Returns icon metadata, creator info, tags, and download URLs.',
      inputSchema: {
        type: 'object',
        properties: {
          icon_id: {
            type: 'number',
            description: 'The unique ID of the icon',
          },
          thumbnail_size: {
            type: 'number',
            enum: [42, 84, 200],
            description: 'Thumbnail size to return (42, 84, or 200 pixels)',
          },
        },
        required: ['icon_id'],
      },
    },
  • TypeScript interface defining input parameters for the getIcon API method.
    export interface GetIconParams {
      icon_id: number;
      thumbnail_size?: 42 | 84 | 200;
    }
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 the return content ('metadata, creator info, tags, and download URLs') but doesn't cover critical aspects like authentication needs, rate limits, error handling, or whether it's a read-only operation. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with the core purpose stated first and return details added efficiently. Both sentences earn their place by clarifying the action and output. It could be slightly improved by integrating usage context, but it avoids waste and is well-structured.

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 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and return values but lacks behavioral details and usage guidelines. Without annotations or output schema, it should do more to compensate, but it's not entirely incomplete.

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%, so the schema already documents both parameters ('icon_id' and 'thumbnail_size') with descriptions and enum values. The description adds no additional parameter semantics beyond what the schema provides, such as format details or usage examples. 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 tool's purpose: 'Get detailed information about a specific icon by its ID.' It specifies the verb ('Get'), resource ('icon'), and identifier method ('by its ID'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_collection' or 'search_icons', 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. It doesn't mention sibling tools like 'get_collection' for collection-level data or 'search_icons' for broader queries, nor does it specify prerequisites or exclusions. Usage is implied only by the purpose statement, lacking explicit 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/sgup/noun-project-mcp'

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