Skip to main content
Glama

emojihub_by_category

Read-onlyIdempotent

Browse emojis by category to find smileys, animals, food, and more. Specify a category slug to retrieve matching emojis for use in apps, messages, or agent workflows.

Instructions

Browse emojis by category (smileys, animals, food, etc.).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "emojihub_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCategory slug (e.g. smileys-and-people, animals-and-nature)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are organized by category, but does not describe return format, pagination, or whether all matching emojis are returned.

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?

A single short sentence front-loads the resource and filtering dimension with no wasted words. It is appropriately sized for a simple one-parameter lookup tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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

For a simple read-only category browse tool with full schema coverage and annotations, the description is nearly complete. A minor gap is that it does not explicitly point to a category-list source or clarify whether output includes all emojis in the category.

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%, and the category parameter is already documented with examples such as smileys-and-people and animals-and-nature. The description's category examples add little beyond the schema, so baseline 3 is appropriate.

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 states a clear verb and resource: browse emojis by category. It distinguishes this from retrieving a random emoji, but does not explicitly name sibling tools such as emojihub_random or emoji_lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'by category', but the description gives no explicit guidance on when to choose this tool over emojihub_random or emoji_lookup. The agent must infer the selection rule from the tool name and description alone.

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

Deploy Server

Other Tools